File management apparatus

ABSTRACT

A file management apparatus, connected to a client terminal via a network, includes a file receiving unit that receives a file transmitted from the client terminal; an image processing unit that generates bitmap data and thumbnail data according to the file; a file storage unit that stores therein each of the bitmap data and the thumbnail data in association with the file; a receiving unit that receives a file retrieval instruction transmitted from the client terminal; a determining unit that determines a type of the client terminal or a type of application that runs on the client terminal, based on the file retrieval instruction; and an output unit that outputs one of the file, the bitmap data, and the thumbnail data stored in the file storage unit according to a result of determination.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to and incorporates by reference the entire contents of Japanese Patent Application No. 2009-112355 filed in Japan on May 1, 2009. The present application incorporates by reference the entire contents of Japanese Patent Application No. 2008-124060 filed in Japan on May 9, 2008.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a technology for managing files in a file management apparatus.

2. Description of the Related Art

With widespread use of information equipments, such as personal computers (PCs), digital cameras, and cell-phones, documents and images are increasingly handled in computerized format (hereinafter, a computerized document, image, or the like is referred to as a “file”). Such files are managed by the information equipments such that a user can retrieve and operate desired files by operating the information equipments.

One technique of managing files is to use a tree structure, in which folders are nested, as employed in WINDOWS (registered trademark) that runs as operating system (OS) in typical PCs. With this configuration, retrieval of a desired file is generally performed by top-down search or bottom-up search.

Conventionally, various techniques of displaying thumbnail images and/or icon images as visual representation of files and/or folders so that files can be managed intuitively have been proposed. For example, Japanese Patent Application Laid-open No. 2006-268295 discloses a technique directed to a user interface, with which icon image representing a plurality of folders at a higher level in hierarchy are laterally arranged in a higher-level display portion of a screen and thumbnail images representing a plurality of files that are at a lower level in the hierarchy and belong to a folder at a specific position are arranged in a lower-level display portion along a substantially “<” line such that a thumbnail image positioned at a specific position corresponding to a corner of the line is relatively enlarged so that a user can have conceptual understanding of scrolling of the thumbnail images in response to operation performed by the user.

However, in the conventional technology, because files are managed with respect to each folder nested in a tree structure, file management is performed with reference to the depth direction of the structure. Therefore, the greater the depth of the level of a folder in the hierarchy, the more complicated the operation to reach the folder becomes, which is disadvantageous. Furthermore, a folder corresponding to one node and another folder corresponding to another node are provided in a different position (level) in the same tree structure, which makes it difficult to intuitively make sense of the relationship between the folders.

The present invention is made in view of the above, and an object of the present invention is to provide a file management apparatus.

SUMMARY OF THE INVENTION

It is an object of the present invention to at least partially solve the problems in the conventional technology.

According to one aspect of the present invention, there is provided a file management apparatus connected to a client terminal via a network, the file management apparatus including: a file receiving unit that receives a file transmitted from the client terminal; an image processing unit that generates bitmap data and thumbnail data according to the file received by the file receiving unit; a file storage unit that stores therein each of the bitmap data and the thumbnail data generated by the image processing unit, in association with the file; a receiving unit that receives a file retrieval instruction transmitted from the client terminal; a determining unit that determines a type of the client terminal or a type of application that runs on the client terminal, based on the file retrieval instruction received by the receiving unit; and an output unit that outputs one of the file, the bitmap data, and the thumbnail data stored in the file storage unit according to a result of determination performed by the determining unit.

The above and other objects, features, advantages and technical and industrial significance of this invention will be better understood by reading the following detailed description of presently preferred embodiments of the invention, when considered in connection with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a hardware configuration of a file management apparatus;

FIG. 2 is a block diagram illustrating a functional configuration of the file management apparatus;

FIG. 3 is a diagram illustrating an example of a folder structure for storing setting information;

FIG. 4 is a diagram illustrating an example of contents of place map information;

FIG. 5 is a diagram illustrating an example of a place map screen;

FIG. 6 is a diagram illustrating an example of a place view screen;

FIG. 7 is a diagram illustrating how interface screens are switched from one to the other;

FIG. 8 is a diagram illustrating an example of an entry support screen;

FIG. 9 is diagram illustrating another example of the entry support screen;

FIGS. 10 to 14 are diagrams for explaining how a place matrix is reconfigured;

FIG. 15 is a flowchart of a procedure of a whole process performed by the file management apparatus;

FIG. 16 is a flowchart of a procedure of a place-map-screen display process;

FIG. 17 is a flowchart of a procedure of a place-view-screen display process;

FIG. 18 is a flowchart of a procedure of a place-matrix reconfiguration process;

FIG. 19 is a flowchart of a procedure of an edge determination process;

FIG. 20 is a flowchart of a procedure of a registration-status determination process;

FIG. 21 is a flowchart of a procedure of an adjacency determination process;

FIG. 22 is a flowchart of a procedure of a map search process;

FIG. 23 is a flowchart of a procedure of a layer search process;

FIG. 24 is a flowchart of a procedure of a place search process;

FIG. 25 is a perspective view of the file management apparatus;

FIG. 26 is a block diagram illustrating a configuration of a file management system;

FIG. 27 is a diagram illustrating a hardware configuration of a file management server;

FIG. 28 is a block diagram illustrating a functional configuration of the file management server;

FIG. 29 is a diagram illustrating an example of a folder structure for storing setting information;

FIG. 30 is a diagram illustrating a hardware configuration of a client terminal;

FIG. 31 is a block diagram illustrating a functional configuration of the client terminal;

FIG. 32 is a diagram illustrating an example of a login screen;

FIG. 33 is a diagram illustrating an example of a place map screen;

FIG. 34 is a flowchart illustrating a flow of a process for displaying a place map screen by the file management server and the client terminal;

FIG. 35 is a diagram illustrating an example of a support screen for registering a place name;

FIG. 36 is a diagram illustrating an example of a support screen for selecting an icon image;

FIG. 37 is a diagram illustrating an example of a place map screen;

FIG. 38 is a flowchart illustrating a flow of a process for changing setting of a shared place by the file management server and the client terminal;

FIG. 39 is a diagram illustrating an example of a support screen for setting a community member;

FIG. 40 is a flowchart illustrating a flow of a process for participation to the shared place, which is performed by the file management server and the client terminal;

FIG. 41 is a diagram illustrating an example of a screen for confirming participation to the shared place;

FIG. 42 is a flowchart illustrating a flow of a process for displaying a place view screen by the file management server and the client terminal;

FIG. 43 is a diagram illustrating an example of a place view screen;

FIG. 44 is a schematic diagram of a place map screen;

FIGS. 45 to 47 are schematic diagrams of place view screens;

FIGS. 48 to 51 are diagrams illustrating examples of place view screens;

FIG. 52 is a diagram illustrating an example of a support screen for registering a file;

FIG. 53 is a diagram illustrating an example of a screen for representing file upload status;

FIG. 54 is a flowchart illustrating a procedure of a file registration process;

FIG. 55 is a flowchart illustrating a procedure of a file deletion process;

FIG. 56 is a flowchart illustrating a flow of a process for viewing a file, performed by the file management server and the client terminal;

FIGS. 57 to 60 are diagrams illustrating examples of file view screens;

FIGS. 61 to 63 are schematic diagrams of file view screens;

FIG. 64 is a diagram illustrating a system according to a third embodiment of the present invention;

FIG. 65 is a diagram illustrating a hierarchical structure of contents data;

FIG. 66 is a diagram illustrating a connection relation from a client terminal to an image processing server; and

FIG. 67 is a diagram illustrating an internal block of the image processing server and its input/output data.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Exemplary embodiments of the present invention are explained in detail below with reference to the accompanying drawings.

First Embodiment

FIG. 1 is a block diagram illustrating a hardware configuration of a file management apparatus 100 according to a first embodiment of the present invention. As illustrated in the figure, the file management apparatus 100 includes a central processing unit (CPU) 11, a read only memory (ROM) 12, a random access memory (RAM) 13, an operating unit 14 that includes an input device such as a mouse and a keyboard, a display unit 15 that includes a display device such as a liquid crystal display monitor, a storage unit 16 that includes a storage device such as a hard disk drive (HDD), an interface (I/F) unit 17 that controls communication with external devices, an adapter unit 18 to which an auxiliary storage device such as a memory card is detachably attached, and a bus 19 that connects the above units to one another, and the hardware configuration thereof is realized by typical computers. The operating unit 14, the display unit 15, and the adapter unit 18 among the configurations illustrated in FIG. 1 are not mandatory for the configuration of the file management apparatus 100. Therefore, they can be removed from the configuration depending on use environments, usage, and the like.

The ROM 12 and the storage unit 16 store therein various computer programs and various types of data. The CPU 11 loads the computer programs from the ROM 12 and the storage unit 16 onto the RAM 13, and executes the loaded computer programs to control the file management apparatus 100 and realize various functional units, which will be described later.

The storage unit 16 uses a predetermined folder structure for storing and managing various setting information used for displaying user interfaces that are support tools for managing files. It is assumed that the “file” is computerized data such as text data, image data, or video data, and previously stored in a predetermined storage area in the storage unit 16. A storage location of the file is not limited to those inside the storage unit 16. For example, the file can be stored in external devices connected to the file management apparatus 100 via the I/F unit 17, or can be stored in auxiliary storage devices connected to the file management apparatus 100 via the adapter unit 18. Detailed explanation about the setting information stored and managed by the storage unit 16 will be given later.

Next, a functional configuration of the file management apparatus 100 is described below. FIG. 2 is a block diagram illustrating the functional configuration of the file management apparatus 100. The file management apparatus 100 includes a display control unit 21, a setting changing unit 22, a place-matrix reconfiguring unit 23, and a searching unit 24, as functional units realized by cooperative execution between computer programs stored in the ROM 12 and the storage unit 16, and the CPU 11.

The display control unit 21 reads various types of setting information from the storage unit 16, and displays user interfaces (GUI) to be used as support tools for managing files on the display unit 15 based on the setting information. Explanation about the user interfaces displayed by the display control unit 21 is given below.

First, the folder structure constructed in the storage unit 16 for storing the setting information for displaying the user interfaces is described below with reference to FIG. 3. As illustrated in the figure, the storage unit 16 has a tree folder structure for storing the setting information. The folder structure is constituted of a map managing section 200 for storing setting information about displaying a place map screen and a place managing section 300 for storing setting information about a place. The place map screen and the place will be described in detail later.

The map managing section 200 contains a “Mapconf” folder that serves as a root folder of the map managing section 200. The “Mapconf” folder stores therein setting information (placeMap.xml) about the place map screen to be described later. The “placeMap.xml” is described below with reference to FIGS. 4 and 5.

FIG. 4 is a diagram illustrating an example of contents of the “placeMap.xml”. As illustrated in the figure, the “placeMap.xml” is written in XML format (see the first row in the “placeMap.xml”). The “placeMap.xml” contains a plurality of layer settings 201, each of which is constituted of a start tag <layer name=“X”, tag=“Y> and an end tag </layer>. It is assumed here that each of “X” and “Y” means null or arbitrary character string. A tag on the second line of the “placeMap.xml” contains “updateTime” indicating date and time at which the “placeMap.xml” was updated, and “preCurrentID” indicating a place name of a place that was operated just before the end of the previous operation. The “placeMap.xml” corresponds to arrangement information. Hereinafter, the “placeMap.xml” is referred to as place map information.

The display control unit 21 sequentially reads the layer settings 201 contained in the place map information, and displays a user interface as shown in FIG. 5 (hereinafter, referred to as a “place map screen”) on the display unit 15 based on setting contents of each of the layer settings 201. Specifically, the display control unit 21 sequentially displays a layer (hereinafter, referred to as an “area L” as appropriate) corresponding to each of the layer settings 201, from an upper portion of the place map screen in order of position of the layer settings 201 contained (stored) in the place map information. That is, the order of the layer settings 201 contained in the place map information has a direct relationship with a drawing position (display position) of a layer.

When a layer name is registered in the layer setting 201, that is, if arbitrary character string is registered instead of “X” in “layer name=“X””, the display control unit 21 draws the character string in the layer name area L1 arranged in the corresponding layer. For example, in the layer setting 201 at the second highest position in the example shown in FIG. 4, “Favorite” is registered in the layer name. In this case, as shown in FIG. 5, the display control unit 21 draws “Favorite” in the layer name area L1 arranged on the second layer corresponding to the layer setting 201 at the second highest position. When “X” is null, that is, when no character string is registered as the layer name, it is possible to display character string indicating an unregistered state (e.g., “untitled”), or null (no display). It is also possible not to display the layer on the display unit 15. However, if any layer name is registered, it is preferable to display the layer name in the layer name area L1.

Each of the layer settings 201 contains a plurality of tags represented by <place ID=“Z”> as shown in FIG. 4 (hereinafter, this tag is referred to as a “place setting 202”). It is assumed here that “Z” means null or arbitrary character string. Each of the place settings 202 corresponds to a place shown in FIG. 5 (hereafter, referred to as an “area P”), which is in the form of a panel and corresponding to a first symbol image. The places are displayed in association with a layer corresponding to the layer setting 201 to which the place settings 202 of those places belong. The display control unit 21 sequentially reads and draws the places each corresponding to one of the place settings 202, from left to write on the place map screen, in order of position of the place settings 202 in the layer setting 201. That is, the order of the place settings 202 contained in the layer setting 201 has a direct relationship with a drawing position of each of the places (display position) on the place map screen.

When a place name is registered in the place setting 202, that is, when arbitrary character string is registered instead of “Z” in “place ID=“Z””, the display control unit 21 draws the character string in a corresponding place. For example, in the layer setting 201 at the second highest position in the example shown in FIG. 4, “My Place” is registered in the place setting 202 on the second line. In this case, as shown in FIG. 5, the display control unit 21 displays “My Place” on a place arranged in the middle of the second layer, that is, the place corresponding to the layer setting 201 at the second highest position and the place setting 202 on the second line.

When “Z” is null, that is, when no place name is registered, it is possible to display character string indicating an unregistered state (e.g., “New Place!”), or display null (no display). Furthermore, when an icon image is registered in association with the place setting 202 as will be described later, the display control unit 21 displays the icon image on a corresponding place.

The layer setting 201 contains “tag=“Y”” in which a layer attribute entered by a user via the operating unit 14 is registered. The “layer attribute” is an index that characterizes each of the layers (the layer settings 201). For example, as shown in the layer setting 201 at the second highest position in the example shown in FIG. 4, arbitrary character string such as “Favorite” and “Photo” can be registered as the layer attribute. The layer attribute registered in the layer is inherited to places contained in this layer, and functions as a master attribute shared by all the places. Explanation about registration of the layer attribute will be given later.

Here, it is assumed that the place map information in the initial state contains a plurality of layer settings (e.g., three) in which layer names and layer attributes are not registered. Furthermore, it is assumed that each of the layer settings in the initial state contains the same number of place settings (more than one (e.g., three)), in which place names and place attributes are not registered.

Referring back to FIG. 3, the place managing section 300 contains various setting information about the above-described places. The place managing section 300 contains a “Placeconf” folder that serves as a root folder of the place managing section 300. The “Placeconf” folder contains “place ID” folders (placeID1, placeID2, . . . ) that are corresponding to file management information, and a “DEF_PLACE” folder.

Each of the “placeID” folders is associated with one of the place settings 202 contained in the place map information of the map managing section 200, so that the corresponding “placeID” folder can be referred to from each of the place settings 202. Specifically, when a place name is registered, a “placeID” folder having a folder name identical to the place name is created, so that each of the place settings 202 is associated with one of the “placeID” folders. Regarding the place setting 202 in which a place name is not registered, the “DEF_PLACE” folder is to be referred to.

The “placeID” folder contains information about files registered in a place displayed based on the place setting 202 corresponding to the same “placeID” folder. Hereinafter, a place displayed based on the place setting 202 corresponding to the “placeID” folder is simply referred to as a corresponding place of the “placeID” folder.

The “placeID” folder contains “place.xml” containing information about a corresponding place of this “placeID” folder. Specifically, a place attribute or comment entered by a user via the operating unit 14 is registered in the “place.xml”. The “place attribute” is an index that characterizes each place, and in which arbitrary character string such as words or symbols can be registered. Explanation about registering the place attribute is given below. Hereinafter, “place.xml” is referred to as place information.

The place attribute can be registered independent of the above-described layer attribute. Compared to the layer attribute that functions as a master attribute shared by all the places, the place attribute functions as a sub attribute that is effective only to each of the places. In other words, in the place map screen, each file can be systematically managed by using the layer and the place (area P) based on the master attribute and the sub attribute.

A “placeicon.jpg” is an icon image (image data) to be drawn in a place. When displaying a place, the display control unit 21 reads the “placeicon.jpg” stored in each of the “placeID” folders and draws the icon image in the corresponding place. An image to be stored as the icon image can be in arbitrary formats. When an icon image is not registered by a user, it is possible to display an image of default image data that is provided in advance.

A “YYYYMM” folder indicates a year and a month when a file is registered in the corresponding place, and is created by the setting changing unit 22 with respect to each year and each month when a file is registered. The “YYYY” represents a year (A.D.) and “MM” represents a month. The “YYYYMM” folder contains a “DD” folder that indicates a day when the file is registered in the corresponding place. The “DD” folder is created by the setting changing unit 22 with respect to each day when a file is registered. In other words, by referring to the “YYYYMM” folder and the “DD” folder, the year and date when the file is registered in the place can be identified.

The “DD” folder contains a “contentsID” folder corresponding to each of files registered in the corresponding place. It is assumed here that the “contentsID” folder is created with a folder name identical to a file name of the file registered in the corresponding place (except extension); however, it is not limited thereto, and the folder name can be others such as a sequence number corresponding to each file.

The “contentsID” folder contains at least “content.xml” that contains information about a file corresponding to the “contentsID” folder, and “thumbnail.jpg” that is a thumbnail image of the file. Specifically, the “content.xml” contains a storage location in which the file corresponding to the “contentsID” folder is actually stored and information about the file such as a file attribute registered in the file, which will be described later. Hereinafter, “content.xml” is referred to as file information.

The “DEF_PLACE” folder contains setting information about a place in an unregistered state that is a state in which a place attribute and a file have not been registered. The “DEF_PLACE” folder stores therein the setting information by using the same structure as that of the “placeID” folder described above. However, in the “DEF_PLACE” folder, the place information does not contain a place attribute, and an “YYYYMM” folder and its subordinate folders are not provided.

When a specific place is specified from the place map screen by a user via the operating unit 14, the display control unit 21 reads a thumbnail image from each of the “contentsID” folders stored in the “placeID” folder corresponding to the specified place, and displays a list of the thumbnail images on the display unit 15. Hereinafter, a screen for displaying the list of the thumbnail images on the display unit 15 is referred to as a place view screen.

FIG. 6 is a diagram illustrating an example of the place view screen displayed on the display unit 15. The figure depicts one display mode in which thumbnail images read from corresponding “contentsID” folders are arranged three-dimensionally. The display control unit 21 sequentially reads and draws thumbnail images stored in corresponding “contentsID” folders in order from the oldest to the latest by referring to the “DD” folder and the “YYYYMM” folder that represent the year and date when each of the files is registered, so that the thumbnail images of the files registered in the corresponding place are displayed in chronological order. In the example shown in FIG. 6, the thumbnail images are arranged in chronological order from the left end to the right end with respect to each line. Furthermore, the thumbnail images are successively arranged from the right corner on the nearest line to the left corner on the line located on the back side. Therefore, chronological relations among the thumbnail images can be indicated from the nearest line toward the farthest line.

In the place view screen shown in FIG. 6, when a cursor C1 is moved upward by a user via the operating unit 14, the display control unit 21 moves arrays of the thumbnail images displayed in the place view screen in a screen-depth direction, so that temporally-newer thumbnail images are displayed in the place view screen. Similarly, when the cursor C1 is moved downward by a user via the operating unit 14, the display control unit 21 moves arrays of the thumbnail images displayed in the place view screen in a near-side direction, so that temporally-older thumbnail images are displayed in the place view screen. Although it is explained in the embodiment that temporally older thumbnail images are arranged on nearer lines, it is possible to arrange temporally newer thumbnail images on nearer lines.

A cursor C2 is used for changing a display angle of thumbnail images. When the cursor C2 is moved upward, the display control unit 21 changes a view point (a depression angle) for displaying arrays of thumbnail images in a horizontal direction in proportion to the amount of move of the cursor C2, so that the display angle is changed. On the other hand, when the cursor C2 is moved downward, the display control unit 21 changes a view point (a depression angle) for displaying arrays of thumbnail images in a perpendicular direction in proportion to the amount of move of the cursor C2, so that the display angle is changed. With this configuration, the display control unit 21 changes an elevation angle of each thumbnail image so that each thumbnail image faces the view point along with movement of the view point.

A cursor C3 is an operating unit for changing a place to be displayed on the place view screen (a place to be a display target) as described above. When the cursor C3 is moved to the left or to the right with respect to the screen via the operating unit 14, the display control unit 21 changes the display target to a place arranged, in the place map screen, on the left side or cn the right side of a place that is currently displayed in the place view screen, according to the move of the cursor C3. Then, the display control unit 21 displays the place view screen with thumbnail images in corresponding “contentsID” folders stored in the “placeID” folder corresponding to the place specified as a new display target. Similarly, when the cursor C3 is moved upward or downward with respect to the screen via the operating unit 14, the display control unit 21 changes the display target to a place arranged, in the place map screen, above or below the place that is currently displayed in the place view screen. Then, the display control unit 21 displays, in the place view screen, thumbnail images in corresponding “contentsID” folders stored in the “placeID” folder corresponding to the place specified as the new display target. Detailed explanation about changing of the place view screen using the cursor C3 will be given in a second embodiment of the present invention.

The display mode of the place view screen is not limited to the example shown in FIG. 6. For example, thumbnail images can be arranged two-dimensionally, or can be displayed with information about files contained in the “content.xml”.

FIG. 7 is a diagram illustrating how user interface screens displayed by the display control unit 21 are switched from one to the other. In the figure, G1 denotes a place map screen, and G21 to G23 denote the place view screens in different display modes in which a place specified from the place map screen G1 is displayed. Arrows shown in the figure indicate relationships of switching of the screens from one to the other. Explanation about reference symbols G31 to G33 will be given later.

When a specific place is specified from the place map screen G1 by a user via the operating unit 14, the display control unit 21 displays the place view screen with the specified place by using one of the display modes G21 to G23.

The place view screen G21 represents a display mode for arranging thumbnail images three-dimensionally as explained with reference to FIG. 6. The place view screen G22 represents a display mode for arranging thumbnail images two-dimensionally in chronological order from left to right and from top to bottom with respect to the screen. The place view screen G23 represents a display mode for displaying thumbnail images with file information of files corresponding to the thumbnail images in chronological order from top to bottom with respect to the screen. The place view screens (display modes) can be selectively changed from one to the other by a user via the operating unit 14. That is, the display control unit 21 selectively changes the display modes of the place view screens according to a request received from a user via the operating unit 14.

When a user instructs to display a specific file (a thumbnail image) from among files displayed on the place view screen via the operating unit 14, the display control unit 21 refers to a storage location in the file information of the specified thumbnail image, reads an original file corresponding to the specified thumbnail image from the storage location, and then displays the read original file on the display unit 15. Hereinafter, a screen for displaying the file on the display unit 15 is referred to as a file view screen.

The file view screen is described with reference to FIG. 7. In the figure, G31 to G33 denote the file view screens in different display modes to be displayed when display of a specific thumbnail image in the place view screen is instructed.

The file view screen G31 represents a display mode for displaying both the specified file and thumbnail images of all the files stored in the same place. In this display mode, when the specified file contains a plurality of pages, thumbnail images of the pages are displayed on the left side of the screen. It is possible to store a thumbnail image of each page in advance in the “contentsID” folder, or it is possible to create the thumbnail image every time an original file is read.

The file view screens G32 and G33 represent display modes for displaying only the specified file without displaying thumbnail images of other files. The file view screen G32 displays pages contained in the specified file one by one while the file view screen G33 displays a list of thumbnail images of all pages contained in the specified file. It is possible to store the thumbnail image of each page can in advance in the “contentsID” folder, or it is possible to create the thumbnail image every time an original file is read.

The file view screens G31 to G33 can be selectively changed from one to the other via the operating unit 14. The display control unit 21 selectively changes the display modes of the file view screens according to contents of instructions input via the operating unit 14.

Referring back to FIG. 2, the setting changing unit 22 changes setting information stored in the storage unit 16 according to operation contents instructed by a user via the operating unit 14. Operation performed by the setting changing unit 22 is described in detail below.

Registration, change, and deletion of a layer name are described below. A user is allowed to register, change, and delete a layer name of a specified layer displayed on the place map screen by using the operating unit 14. When receiving an instruction to register, change, or delete the layer name of the specified layer via the operating unit 14, the setting changing unit 22 displays an entry support screen as shown in FIG. 8 for the layer for which registration, change, or deletion of the layer name is instructed. In FIG. 8, an area A11 is used for entering a layer name, and an area A12 is used for entering a layer attribute, which will be described later. When a button B11 is pressed by the user, character string entered in the areas A11 and A12 are sent to the setting changing unit 22. On the other hand, when a button B12 is pressed by the user, the setting changing unit 22 closes the entry support screen. The entry support screen shown in FIG. 8 is one example and its screen configuration is not limited to this illustrated example.

When the user enters the layer name and presses the button B11 in the entry support screen shown in FIG. 8, the setting changing unit 22 writes the layer name entered in the area A11 over “X” in the layer setting 201 (layer name=“X”) corresponding to the layer specified by the user. At this time, when null is entered in the area A11, it means that the layer name is deleted. When a layer name is already registered, it is possible to display the layer name read from the layer setting 201 (layer name=“X”) of the specified layer in the area A11.

A user is also allowed to delete a layer itself for a specific layer displayed on the place map screen. When receiving an instruction for deleting the specified layer itself via the operating unit 14, the setting changing unit 22 deletes the layer setting 201 corresponding to the specified layer from the place map information stored in the map managing section 200.

Registration, change, and deletion of a layer attribute are described below. A user is allowed to instruct registration, change, and deletion of a layer attribute of a specified layer displayed on the place map screen by using the operating unit 14. When receiving the instruction to register, change, or delete the layer attribute of the specified layer via the operating unit 14, the setting changing unit 22 displays the entry support screen shown in FIG. 8 with respect to the specified layer.

When the user enters the layer attribute and presses the button B11 in the entry support screen shown in FIG. 8, the setting changing unit 22 writes the character string entered in the area A12 over “Y” in the layer setting 201 (tag=“Y”) corresponding to the layer specified by the user, among the place map information stored in the map managing section 200. At this state, when null is entered in the area A12, it means that the layer attribute is deleted. When a layer attribute is already registered, it is possible to display the layer attribute read from the layer setting 201 (tag=“Y”) of the specified layer in the area A12.

Registration, change, and deletion of a place name are described below. A user is allowed to register, change, and delete a place name of a specified place displayed on the place map screen by using the operating unit 14. When receiving an instruction to register, change, or delete the place name of the specified place via the operating unit 14, the setting changing unit 22 displays an entry support screen shown in FIG. 9 with respect to the specified place.

In FIG. 9, an area A21 is used for displaying a layer name of a layer to which the specified place belongs. Specifically, a layer name (layer name=“X”) read from the layer setting associated with the place setting of the specified place is displayed in read-only mode in the area A21. An area A22 is used for entering a place name, an area A23 is used for entering a place attribute, and an area A24 is used for entering arbitrary character string as comments or the like to be associated with the place.

A “browse” button B23 is used for displaying a support screen for selecting an icon image when the icon image is to be registered, which will be described later. When a button B21 is pressed by the user, contents entered and set in the support screen are sent to the setting changing unit 22. On the other hand, when a button B12 is pressed, the setting changing unit 22 closes the support screen. The support screen shown in FIG. 9 is one example, and its screen configuration is not limited to this illustrated example.

When the user enters the place name and presses the button B21 in the support screen as shown in FIG. 9, the setting changing unit 22 writes the place name entered in the area A21 over “Z” in the place setting 202 (place ID=“Z”) corresponding to the place specified by the user. Furthermore, the setting changing unit 22 creates a “placeID” folder whose folder name is identical to the place name entered in the area A22, in a “Placeconf” folder.

When the place name is changed, the “placeID” folder having the folder name identical to the place name before being changed is renamed to the changed place name. When null is entered in the area A22, it means that the layer attribute is deleted, the setting changing unit 22 deletes the “placeID” folder having the folder name identical to the place for which deletion is instructed. When a place name is already registered, it is possible to display the place name read from the place setting 202 (place ID=“Z”) of a specified place, in the area A22.

When a file is registered in a place without registration of a place name, the setting changing unit 22 writes a predetermined place name (e.g., “No Name”) over “Z” in the place setting 202 (place ID=“Z”) and creates a “placeID” folder with a folder name identical to the predetermined place name in the “Placeconf” folder so as to discriminate it from a place having no registered place name and no registered file. The setting changing unit 22 performs exclusive control to prevent redundant place names.

Registration, change, and deletion of a place attribute are described below. A user is allowed to register, change, and delete a place attribute of a specified place displayed on the place map screen by using the operating unit 14. When receiving an instruction to register, change, or delete the place attribute of the specified place via the operating unit 14, the setting changing unit 22 displays the support screen as shown in FIG. 9 on the display unit 15.

When the user enters the place attribute and presses the button B21 in the entry support screen as shown in FIG. 9, the setting changing unit 22 creates place information (place.xml) in the “placeID” folder corresponding to the specified place, and writes the character string entered in the area A23 as the place attribute in the place information. When null is entered in the area A23, it means that the place attribute is deleted. When a place attribute is already registered in the place information of the specified place, it is possible to display the place attribute read from the place information, in the area A23.

Furthermore, when character string is entered in the area A24 and the button B21 is pressed in the support screen as shown in FIG. 9, the setting changing unit 22 writes the character string entered in the area A24 as a comment in the corresponding place information. When null is entered in the area A24, it means that the comment is deleted. When a comment is already registered in the place information of the specified place, it is possible to display the comment read from the place information, in the area A24.

Registration of an icon image is described below. A user is allowed to register an icon image in a specified place displayed on the place map screen by using the operating unit 14. When receiving an instruction to register an icon image in the specified place via the operating unit 14, the setting changing unit 22 displays the support screen shown in FIG. 9.

When the user presses the button B23 in the support screen shown in FIG. 9, the setting changing unit 22 displays a support screen for selecting an icon image on the display unit 15. When an icon image is selected via the operating unit 14, the setting changing unit 22 reads an image from a storage location of the selected icon image and displays the image in an area A25.

When the user specifies the icon image and presses the button B21 in the support screen shown in FIG. 9, the setting changing unit 22 copies the specified icon image to the “placeID” folder of the specified place, and stores the icon image as “placeicon.jpg” in the “placeID” folder. When an icon image is already stored in the “placeID” folder corresponding to the specified place, it is possible to display the icon image read from this “placeID” folder, in the area A25.

Registration and deletion of a file are described below. A user is allowed to register one or more files in a specified place having a registered place name among places displayed on the place map screen. Here, “registration of files” means that a plurality of files is managed in association with each place. Any methods can be applied to register files. For example, it is possible to instruct registration of files by dragging and dropping one or more files in a place, and the like. It is also possible to instruct the registration via the place view screen to be described later.

When receiving an instruction to register a file in a specified place, the setting changing unit 22 creates a “YYYYMM” indicating a current year and month in the “placeID” folder corresponding to the specified place. Then, the setting changing unit 22 creates a “DD” folder indicating a current day in the “YYYYMM” folder.

The setting changing unit 22 creates, in the created “DD” folder, “contentsID” folders with folder names identical to file names of respective registered files. Then, the setting changing unit 22 stores, in each “contentsID” folder, file information (content.xml) containing at least a storage location of a corresponding file, and a thumbnail image created from the corresponding file. Time information (year and date) is obtained by a timing unit (not shown) that counts year and date through counting of time. In the embodiment, it is assumed that an actual content of a file is stored in a different storage area. However, the actual contents of the registered file can be stored in the corresponding “contentsID” folder.

When receiving an instruction to delete a specified file registered in the place via the operating unit 14, the setting changing unit 22 deletes the “contentsID” folder corresponding to the specified file from the “placeID” folder corresponding to the place.

Operation for moving a place in the place map screen is described below. A user is allowed to move a place from one position to the other in the place map screen by using the operating unit 14. When receiving, via the operating unit 14, an instruction to move a specified place to a position of another place (a target place) among places displayed on the place map screen, the setting changing unit 22 exchanges a position of the place setting of the specified place with a position of the place setting of the target place in the place map information, so that the position of the specified place is moved to the position of the target place.

In this manner, the setting changing unit 22 updates the setting information stored in the storage unit 16 depending on operation contents received by the user via the operating unit 14.

Referring back to FIG. 2, the place-matrix reconfiguring unit 23 changes the number of layers and places contained in a place matrix on the place map screen based on setting contents of the place map information changed by the setting changing unit 22, and reconfigures the place matrix according to a predetermined rule (hereinafter, referred to as “neighborhood rule”). Here, the “place matrix” means a matrix of places arranged in multiple-stage layers in the place map screen. Reconfiguration of a place matrix due to addition, deletion, and move of a place is described below.

Operation for expanding a place matrix due to registration of a place name is described below. When a place name is registered by the setting changing unit 22, the place-matrix reconfiguring unit 23 determines whether a place whose place name has been just registered is on an edge of the place matrix. Specifically, the place-matrix reconfiguring unit 23 determines whether the place setting corresponding to the place whose place name has been just registered is contained in either the highest position or the lowest position in the layer setting, or whether the layer setting containing this place setting is contained in either the highest position or the lowest position in the place map information, so that the place-matrix reconfiguring unit 23 determines whether the place whose place name has been just registered is on the edge of the place matrix. Hereinafter, the above-described determination is referred to as “edge determination”.

When determining that the place whose place name has been just registered is on the edge of the place matrix as a result of the edge determination, the place-matrix reconfiguring unit 23 expands the place matrix by adding a layer (a place row) or a place column in an unregistered state to an outer portion of the place. Operation performed by the place-matrix reconfiguring unit 23 when a place name is registered is described below with reference to FIGS. 5, and 10 to 12.

FIG. 5 is a schematic diagram of the place map screen containing three layers having three places (areas P), that is, a place matrix with three rows and three columns. In the figure, when receiving an instruction to register a place name “Family” in any place contained in the top layer, e.g., in the center layer, via the operating unit 14, the setting changing unit 22 registers the place name in the specified place in the manner described above. At this time, the place-matrix reconfiguring unit 23 performs the edge determination and determines that the place whose place name has been just registered is in the top layer of the place matrix. Therefore, as shown in FIG. 10, the place-matrix reconfiguring unit 23 adds a new layer (place row) above this place.

Specifically, the place-matrix reconfiguring unit 23 adds new layer setting 201 to the highest position, that is, above the layer setting 201 currently at the highest position, in the place map information. Consequently, a new layer (place row) is added to a row above the currently top layer containing the place whose place name has been just registered. At this time, the layer setting 201 of the new layer is configured such that the same number of the place settings 202 as those in the other layer settings 201 is contained so as to shape the whole place matrix into a rectangle. When a place name is registered in a place contained in the bottom layer of the place matrix, the place-matrix reconfiguring unit 23 adds the layer setting 201 to the lowest position, that is, below the layer setting 201 currently at the lowest position in the place map information.

When receiving an instruction to register a place name in a place on the right edge of any layers in the place matrix shown in FIG. 5, e.g., when receiving an instruction to register a place name “CPS-PT” in a place on the right edge of a middle layer in the place matrix, via the operating unit 14, the setting changing unit 22 registers the place name in the specified place. At this time, the place-matrix reconfiguring unit 23 determines that the place whose place name has been just registered is on the right edge of the place matrix as a result of the edge determination. Therefore, as shown in FIG. 11, the place-matrix reconfiguring unit 23 adds a new column (place column) in a column on the right of this place.

Specifically, the place-matrix reconfiguring unit 23 adds the place setting 202 in an unregistered state to the lowest position, that is, below the place setting 202 currently at the lowest position in each of the layer settings 201 in the place map information. Consequently, a new place column is added in a column on the right of the place whose place name has been just registered. When a place name is registered in a place on the left edge of the place in any layers in the place matrix shown in FIG. 5, the place-matrix reconfiguring unit 23 adds the place setting 202 in an unregistered state to the highest position, that is, above the place setting 202 currently at the highest position in each of the layer settings 201 in the place map information.

When receiving an instruction to register a place name in a place at the corner of the place matrix shown in FIG. 5, e.g., when receiving an instruction to register a place name “CPS-PT” in a place on the right edge of the bottom layer in the place matrix, via the operating unit 14, the setting changing unit 22 registers the place name in the specified place. At this time, the place-matrix reconfiguring unit 23 determines that the place whose place name has been just registered is at the lower right corner of the place matrix as a result of the edge determination. Therefore, as shown in FIG. 12, the place-matrix reconfiguring unit 23 adds a new layer (place row) below that place and a new place column in a column on the right of this place.

Specifically, the place-matrix reconfiguring unit 23 adds the layer setting 201 in an unregistered state to the lowest position, that is, below the layer setting 201 currently at the lowest position in the place map information, and adds the place setting 202 in an unregistered state to the lowest position, that is, below the place setting 202 currently at the lowest position in each of the layer settings 201 in the place map information.

When a place name is registered in a place at the upper left corner of the place matrix, the place-matrix reconfiguring unit 23 adds the layer setting 201 in an unregistered state to the highest position, that is, above the layer setting 201 currently at the highest position in the place map information, and adds the place setting 202 in an unregistered state to the highest position, that is, above the place setting 202 currently at the highest position in each of the layer settings 201 in the place map information. Furthermore, when a place name is registered in a place at the upper right corner of the place matrix, the place-matrix reconfiguring unit 23 adds the layer setting 201 in an unregistered state to the highest position, that is, above the layer setting 201 currently at the highest position in the place map information, and adds the place setting 202 in an unregistered state to the lowest position, that is, below the place setting 202 currently at the lowest position in each of the layer settings 201 in the place map information. Moreover, when a place name is registered in a place at the lower left corner of the place matrix, the place-matrix reconfiguring unit 23 adds the layer setting 201 in an unregistered state to the lowest position, that is, below the layer setting 201 currently at the lowest position in the place map information, and adds the place setting 202 in an unregistered state to the highest position, that is, above the place setting 202 currently at the highest position in each of the layer settings 201 in the place map information.

In this manner, the place-matrix reconfiguring unit 23 expands the place matrix along with the registration of the place name. Therefore, it is possible to reduce load on operations for adding layers and places by a user, so that user's usability can be improved. Furthermore, the place matrix is reconfigured so that places having no registered place names are arranged on each edge of the place matrix. Therefore, places having registered place names are displayed at around the center of the place matrix, so that high level of visibility can be attained in the display. In the example described above, a layer is automatically added when a place name is registered in a place on the upper edge or the lower edge of the place matrix. However, when a user explicitly instructs to add a layer via the operating unit 14, the layer can be added independent of registration of place names.

Operation for reducing a place matrix due to deletion of a place name is described below. When a place name is deleted from a specified place by the setting changing unit 22, in the place matrix, the place-matrix reconfiguring unit 23 determines whether a place having the registered place name is contained in the same row and the same column of the place.

Specifically, the place-matrix reconfiguring unit 23 identifies, from the place map information, the place setting 202 corresponding to the place whose place name has been just deleted. Then, the place-matrix reconfiguring unit 23 determines whether the place setting 202 with a registered place name is contained in the layer setting 201 containing the identified place setting 202. Furthermore, the place-matrix reconfiguring unit 23 detects a rank of the identified place setting 202 in the layer setting 201, and determines whether a place name is registered in the place setting 202 at the same rank in each of the other layer settings 201. Hereinafter, the above-mentioned processes are collectively referred to as a registration-status determination.

Furthermore, the place-matrix reconfiguring unit 23 deletes a place row (layer) and a place column determined as not having places with registered place names as a result of the registration-status determination, so that the place matrix is reduced. Operation performed by the place-matrix reconfiguring unit 23 when the place name is deleted is described below with reference to FIGS. 12 and 13.

When receiving an instruction to delete a place, e.g., a place (CPS-PT) in the third layer and in the second column from the right with respect to the place matrix shown in FIG. 12, the setting changing unit 22 deletes the place name from the specified place. At this time, the setting changing unit 22 performs the registration-status determination and determines that places having registered place names are not contained in both the row and the column containing the place whose place name has been just deleted. Therefore, the setting changing unit 22 deletes the layer corresponding to the row, and places contained in the column, with respect to the specified place. As a result, the place matrix is reduced to the state shown in FIG. 5.

Specifically, the setting changing unit 22 deletes the place setting 202 at the rank detected by the registration-status determination from each of the layer settings 201 in the place map information, and deletes the layer setting 201 of the layer containing the place whose place name has been deleted. When a layer name is registered in a place row in which the place instructed to be deleted is contained, i.e., in a layer to which this place belongs, it is possible not to delete the layer as shown in FIG. 13. It is also possible not to delete layers regardless of whether a layer name is registered, and maintain the layers until a user explicitly instructs to delete a layer. In this case, when a place having a registered place name is contained in places belonging to a layer, it is possible to limit deletion of this layer until the place name is deleted.

In this manner, the place matrix is dynamically reconfigured according to deletion of the place name. Therefore, it is possible to reduce load on explicit operations such as deletion of layers and places by a user, so that user's usability can be improved. It is also possible to prevent increase in number of places whose place names are not registered. As a result, a high level of visibility can be attained in the display.

Operation for expanding and reducing a place matrix due to move of a place is described below. When a specific place is moved to another position by the setting changing unit 22, the place-matrix reconfiguring unit 23 determines whether a position of the place before move is adjacent to a place on the edge of the place matrix.

Specifically, the place-matrix reconfiguring unit 23 identifies the place setting 202 corresponding to a place before move from the place map information. Then, the place-matrix reconfiguring unit 23 determines whether the identified place setting 202 is either at the second highest position or at the second lowest position in the layer setting 201, and also determines whether the layer setting 201 containing the identified place setting 202 is either at the second highest position or the second lowest position in the place map information so as to determine whether the place before move is adjacent to a place on the edge of the place matrix. Hereinafter, the above-described process is referred to as an adjacency determination.

When determining through the adjacency determination that the place before move is adjacent to a place on the edge of the place matrix, the place-matrix reconfiguring unit 23 performs the registration-status determination to determine whether a place having a registered place name is contained in the row and the column containing the place before move. When determining through the registration-status determination that a place having the registered place name is not contained in the row and the column, the place-matrix reconfiguring unit 23 deletes the place from the row and the column.

The place-matrix reconfiguring unit 23 also determines whether a position of the place after move is on the edge of the place matrix. When determining that the position of the place after move is on the edge of the place matrix, the place-matrix reconfiguring unit 23 adds a place row (layer) or a place column in an unregistered state to an outer portion of the place after move. Operation for adding the place row and the place column is the same as that performed when the place matrix is reconfigured along with registration of a place name as described above, and the same explanation is not repeated. Operation performed by the place-matrix reconfiguring unit 23 when the place is moved is described in detail below with reference to FIGS. 12, 14, and 10.

When receiving an instruction to move a place, e.g., an instruction to move a place (CPS-PT) in the third layer and in the second column from the right with respect to the place matrix shown in FIG. 12 to the right side, the setting changing unit 22 exchanges a position of the place setting 202 of the place before move with a position of the place setting 202 of the place after move in the place map information, so that the place is moved to the right side. At this time, the place-matrix reconfiguring unit 23 performs the edge determination and determines that the place after move is on the right edge of the place matrix. Therefore, as shown in FIG. 14, the place-matrix reconfiguring unit 23 adds a new place column in a column on the right of the place after move.

When receiving an instruction to move a place, e.g., an instruction to move a place (CPS-PT) in the third layer and in the second column from the right with respect to the place matrix shown in FIG. 12 to the left side, the setting changing unit 22 exchanges a position of the place setting 202 of the place before move with a position of the place setting 202 of the place after move in the place map information, so that the place is moved to the left side. At this time, the setting changing unit 22 performs the adjacency determination and determines that the place before move is adjacent to a place on the edge of the place matrix and a place having the registered place name is not contained in the place column containing the place before move. Therefore, the setting changing unit 22 deletes the place column containing the place before move. As a result, the place matrix similar to that shown in FIG. 10 is obtained.

In this manner, the place matrix is dynamically reconfigured along with move of a place. Therefore, it is possible to reduce load on explicit operations such as addition and deletion of layers and places by a user, so that user's usability can be improved. It is also possible to prevent increase in number of places whose place names are not registered. As a result, a high level of visibility can be attained in the display.

Referring back to FIG. 2, the searching unit 24 searches for a file corresponding to a search key that is character string received as search criteria from a user via the operating unit 14, based on either one of a layer attribute set in each of layers and a place attribute set in each of places.

Specifically, when one or more layers are specified from the place map screen and then a search key is input, the searching unit 24 sets the specified layers as a search area and searches for a file corresponding to the search key from layer attributes of the specified layers and place attributes of places contained in the specified layers. Then, the searching unit 24 displays a list of thumbnail images of files registered both in the places contained in the layers whose layer attributes correspond to the search key and in the places whose place attributes correspond to the search key, on the display unit 15.

When one or more places are specified from the place map screen and then a search key is input, the searching unit 24 sets the specified places as a search area and searches for a file corresponding to the search key from place attributes of the specified places. Then, the searching unit 24 displays a list of thumbnail images of files registered in the places whose place attributes correspond to the search key, on the display unit 15.

The whole operation performed by the file management apparatus 100 is described below. FIG. 15 is a flowchart illustrating a procedure of the whole process performed by the file management apparatus 100. The display control unit 21 refers to the place map information and performs a place-map-screen display process (Step S11). The place-map-screen display process at Step S11 is described in detail below with reference to FIG. 16.

FIG. 16 is a flowchart illustrating a procedure of the place-map-screen display process. The display control unit 21 selects one layer setting 201 contained in the place map information, as a drawing object to be processed (Step S1111). According to the embodiment, it is assumed that the layer settings 201 are sequentially selected in order of position contained in the place map information from the highest to the lowest. However, what order the layer settings 201 are to be selected is not limited to this example.

The display control unit 21 draws a layer corresponding to the layer setting 201 selected at Step S1111 right below a previously drawn layer (Step S1112). At the initial time when no layers are drawn, a layer selected as a drawing object is drawn in a predetermined position in the display screen.

Then, the display control unit 21 determines whether a layer name is registered in the layer setting 201 being the drawing object (Step S1113). When the display control unit 21 determines that the layer name is not registered (No at Step S1113), process directly proceeds to Step S1115. On the other hand, when determining that the layer name is registered (Yes at Step S1113), the display control unit 21 draws the layer name in the layer name area L1 in the layer drawn at Step S1112 (Step S1114), and process proceeds to Step S1115.

The display control unit 21 selects, as a drawing object to be processed, one place setting 202 contained in the layer setting 201 being as the drawing object (Step S1115). According to the embodiment, it is assumed that the place settings 202 are sequentially selected in order of position contained (stored) in the layer setting 201 from the highest to the lowest. However, what order the place settings 202 are to be selected is not limited to this example.

The display control unit 21 draws a place corresponding to the place setting 202 being the drawing object in a column on the right of a previously drawn place in the layer drawn at Step S1112 (Step S1116). At the initial time when no places are drawn, a place selected as a drawing object is drawn in a predetermined position in the selected layer.

The display control unit 21 determines whether an icon image is stored in the “placeID” folder corresponding to the place setting 202 being the drawing object (Step S1117). When the display control unit 21 determines that the icon image is not stored (No at Step S1117), process directly proceeds to Step S1119. On the other hand, when determining that the icon image is stored (Yes at Step S1117), the display control unit 21 draws the icon image in the place drawn at Step S1116 (Step S1118), and process proceeds to Step S1119.

Then, the display control unit 21 determines whether a place name is registered in the place setting 202 being the drawing object (Step S1119). When the display control unit 21 determines that the place name is not registered (No at Step S1119), process directly proceeds to Step S1121. On the other hand, when determining that the place name is registered (Yes at Step S1119), the display control unit 21 draws the place name in the place drawn at Step S1116 (Step S1120), and process proceeds to Step S1121.

At Step S1121, the display control unit 21 determines whether all the place settings 202 contained in the layer setting 201 being the drawing object have been processed (Step S1121). When the display control unit 21 determines that there is the place setting 202 that has not been processed (No at Step S1121), process returns to Step S1115 for processing the unprocessed place setting 202.

At Step S1121, when determining that all the place settings 202 contained in the layer setting 201 that is being processed as the drawing object have been processed (Yes at Step S1121), the display control unit 21 determines whether all the layer settings 201 contained in the place map information have been processed (Step S1122). When the display control unit 21 determines that there is the layer setting 201 that has not been processed (No at Step S1122), process returns to Step S1111 for processing the unprocessed layer setting 201. On the other hand, when the display control unit 21 determines that all the layer settings 201 have been processed (Yes at Step S1122), process proceeds to Step S12 of FIG. 15.

Referring back to FIG. 15, the display control unit 21 determines whether display of the place view screen of a place specified from places displayed on the place map screen is instructed via the operating unit 14 or not (Step S12). When determining that the display of the place view screen is instructed (Yes at Step S12), the display control unit 21 refers to the “placeID” folder corresponding to the specified place from the place managing section 300 in the storage unit 16, and performs a place-view-screen display process (Step S13). The place-view-screen display process at Step S13 is described in detail below with reference to FIG. 17.

FIG. 17 is a flowchart illustrating a procedure of the place-view-screen display process. The display control unit 21 refers to the “placeID” folder corresponding to a place name of the place specified at Step S12 (Step S1311).

Then, the display control unit 21 sequentially selects each of the “YYYYMM” folders in order from temporally oldest according to the year and the month indicated by that folder, from the “placeID” folder (Step S1312). The display control unit 21 then sequentially selects each of the “DD” folders in order from temporally oldest according to the date indicated by that folder, from the “YYYYMM” folder selected at Step S1312 (Step S1313).

Then, the display control unit 21 reads a thumbnail image from one of the “contentsID” folders stored in the “DD” folder selected at Step S1313 (Step S1314), and draws the thumbnail image read at Step S1314 at a position next to a previously drawn thumbnail image (Step S1315). At the initial time when no thumbnail images are drawn, the read thumbnail image is drawn at a predetermined position in the place view screen.

Then, the display control unit 21 determines whether all the thumbnail images have been read from all the “contentsID” folders in the “DD” folder selected at Step S1313 (Step S1316). When the display control unit 21 determines that there is a “contentsID” folder that has not been processed (No at Step S1316), process returns to Step S1314 for reading thumbnail images from that “contentsID” folder.

On the other hand, at Step S1316, when determining that all the thumbnail images have been read from all the “contentsID” folders (Yes at Step S1316), the display control unit 21 determines whether all the “DD” folders have been selected from the “YYYYMM” folder selected at Step S1312 (Step S1317). When the display control unit 21 determines that there is a “DD” folder that has not been selected (No at Step S1317), process returns to Step S1313 for selecting that “DD” folder.

On the other hand, at Step S1317, when determining that all the “DD” folders have been selected (Yes at Step S1317), the display control unit 21 determines whether all the “YYYYMM” folders have been selected from the “placeID” folder referred to at Step S1311 (Step S1318). When the display control unit 21 determines that there is a “YYYYMM” folder that has not been selected (No at Step S1318), process returns to Step S1312 for selecting that “YYYYMM” folder. On the other hand, when the display control unit 21 determines that all the “YYYYMM” folders have been selected (Yes at Step S1318), process returns to Step S14 of FIG. 15. It is assumed that the place view screen is displayed in one of the display modes of the place view screens G21 to G23 shown in FIG. 7, and the display modes are switched from one to the other according to an instruction input via the operating unit 14.

The display control unit 21 determines whether an instruction to display a file view screen of a thumbnail image specified from among the thumbnail images displayed on the place view screen is input via the operating unit 14 (Step S14). When determining that the instruction to display the file view screen is input (Yes at Step S14), the display control unit 21 refers to contents information of the “contentsID” folder containing the specified thumbnail image, reads a file from a storage location contained in the contents information, and displays the read file in the file view screen on the display unit 15 (Step S15). It is assumed that the file view screen is displayed in one of the display modes of the file view screens G31 to G33 shown in FIG. 7, and the display modes are switched from one to the other according to an instruction input via the operating unit 14.

The display control unit 21 determines whether an instruction to return to the place view screen is input via the operating unit 14 (Step S16). When the display control unit 21 determines that the instruction to return to the place view screen is not input (No at Step S16), process returns to Step S15. On the other hand, when the display control unit 21 determines that the instruction to return to the place view screen is input (Yes at Step S16), process returns to Step S13.

At Step S14, when determining that the instruction to display the file view screen is not received (No at Step S14), the display control unit 21 determines whether an instruction to return to the place map screen is input via the operating unit 14 (Step S17). When the display control unit 21 determines that the instruction to return to the place map screen is not input (No at Step S17), process returns to Step S13. On the other hand, when the display control unit 21 determines that the instruction to return to the place map screen is input (Yes at Step S17), process returns to Step S11.

At Step S12, when the display control unit 21 determines that the instruction to display the place view screen is not input (No at Step S12), the setting changing unit 22 determines whether an instruction to operate the place map screen is input via the operating unit 14 (Step S18). When the setting changing unit 22 determines that the instruction to operate the place map screen is not received (No at Step S18), process returns to Step S11.

On the other hand, at Step S18, when determining that the instruction to operate the place map screen is input (Yes at Step S18), the setting changing unit 22 changes the setting information based on the received operation content (Step S19). The operations to be performed at Step S18 are registration, change, and deletion of layer names, layer attributes, place names, and place attributes; registration and deletion of files; and move of places. The setting information is changed at Step S19 with respect to each of the above operations.

Then, the place-matrix reconfiguring unit 23 determines whether setting content of the place map information is changed due to change of the setting information performed by the setting changing unit 22 at Step S19 (Step S20). When the place-matrix reconfiguring unit 23 determines that the setting content of the place map information is not changed (No at Step S20), process returns to Step S11.

On the other hand, at Step S20, when determining that the setting content of the place map information is changed (Yes at Step S20), the place-matrix reconfiguring unit 23 performs a place-matrix reconfiguration process (Step S21). The place-matrix reconfiguration process is described in detail below with reference to FIGS. 18 to 21.

FIG. 18 is a flowchart illustrating a procedure of the place-matrix reconfiguration process. The place-matrix reconfiguring unit 23 determines, in the process at Step S19, whether a place name is registered (Step S2111). When the place-matrix reconfiguring unit 23 determines that a process other than a process of registering the place name is performed at Step S19 (No at Step S2111), process proceeds to Step S2113.

On the other hand, at Step S2111, when determining that the place name is registered at Step S19 (Yes at Step S2111), the place-matrix reconfiguring unit 23 performs the edge determination process based on the place setting of the place whose place name has been just registered (Step S2112). The edge determination process performed at Step S2112 is described in detail below with reference to FIG. 19.

FIG. 19 is a diagram illustrating a procedure of the edge determination process at Step S2112. The place-matrix reconfiguring unit 23 identifies the place setting 202 corresponding to the place whose place name has been just registered, and the layer setting 201 containing that place setting 202, from the place map information (Step S211211).

Then, the place-matrix reconfiguring unit 23 detects at what position the place setting 202 identified at Step S211211 is contained in the layer setting 201 identified at Step S211211, that is, detects a rank of the place setting 202 (Step S211212). Hereinafter, the rank detected at Step S211212 is referred to as “a place rank”.

Then, the place-matrix reconfiguring unit 23 checks the place rank detected at Step S211212. When determining that the place rank is the highest (HIGHEST at Step S211213), the place-matrix reconfiguring unit 23 adds the place setting 202 in an unregistered state to the highest position, that is, above the place setting 202 currently at the highest position in each of the layer settings 201 contained in the place map information (Step S211214), and process proceeds to Step S211216.

At Step S211213, when determining that the place rank is the lowest (LOWEST at Step S211213), the place-matrix reconfiguring unit 23 adds the place setting 202 in an unregistered state to the lowest position, that is, below the place setting 202 currently at the lowest position in each of the layer settings 201 contained in the place map information (Step S211215), and process proceeds to Step S211216.

At Step S211213, when the place-matrix reconfiguring unit 23 determines that the place rank is neither the highest nor the lowest (OTHERS at Step S211213), process proceeds to Step S211216.

Then, the place-matrix reconfiguring unit 23 detects at what position the layer setting 201 identified at Step S211211 is contained in the place map information, that is, detects a rank of the layer setting 201 (Step S211216). Hereinafter, the rank detected at Step S211216 is referred to as “a layer rank”.

Then, the place-matrix reconfiguring unit 23 checks the layer rank detected at Step S211216. When determining that the layer rank is the highest (HIGHEST at Step S211217), the place-matrix reconfiguring unit 23 adds the layer setting 201 in an unregistered state to the highest position, that is, above the layer setting 201 currently at the highest position in the place map information (Step S211218), and process proceeds to Step S2113 of FIG. 18.

At Step S211217, when determining that the layer rank is the lowest (LOWEST at Step S211217), the place-matrix reconfiguring unit 23 adds the layer setting 201 in an unregistered state to the lowest position, that is, below the layer setting 201 currently at the lowest position in the place map information (Step S211219), and process proceeds to Step S2113 of FIG. 18.

At Step S211217, when the place-matrix reconfiguring unit 23 determines that the layer rank is neither the highest nor the lowest (OTHERS at Step S211217), process proceeds to Step S2113 of FIG. 18.

Referring back to FIG. 18, the place-matrix reconfiguring unit 23 determines whether the place name is deleted in the operation performed at Step S19 (Step S2113). When the place-matrix reconfiguring unit 23 determines that the operation other than deletion of the place name is performed at Step S19 (No at Step S2113), process proceeds to Step S2115.

On the other hand, at Step S2113, when determining that the place name is deleted at Step S19 (Yes at Step S2113), the place-matrix reconfiguring unit 23 performs a registration-status determination process (Step S2114). The registration-status determination process at Step S2114 is described in detail below with reference to FIG. 20.

FIG. 20 is a diagram illustrating a procedure of the registration-status determination process. The place-matrix reconfiguring unit 23 identifies the place setting 202 corresponding to the place whose place name has been deleted, and the layer setting 201 containing that place setting 202, from the place map information (Step S211411).

Then, the place-matrix reconfiguring unit 23 detects at what position the place setting 202 identified at Step S211411 is contained in the layer setting 201 identified at Step S211411, that is, detects the place rank of that place setting 202 (Step S211412). Then, the place-matrix reconfiguring unit 23 determines whether the place setting 202 at the detected place rank in each of the layer settings 201 contains a registered place name (Step S211413). When the place-matrix reconfiguring unit 23 determines that the place setting 202 having the registered place name is contained (Yes at Step S211413), process proceeds to Step S211415.

On the other hand, at Step S211413, when determining that the place setting 202 having the registered place name is not contained (No at Step S211413), the place-matrix reconfiguring unit 23 deletes the place setting 202 at the detected place rank from all the layer settings 201 in the place map information (Step S211414), and process proceeds to Step S211415.

Then, the place-matrix reconfiguring unit 23 determines whether the place setting 202 having the registered place name is contained in the layer setting 201 identified at Step S211411 (Step S211415). When the place-matrix reconfiguring unit 23 determines that the place setting 202 having the registered place name is contained (Yes at Step S211415), process proceeds to Step S2115 of FIG. 18.

On the other hand, at Step S211415, when determining that the place setting 202 having the registered place name is not contained (No at Step S211415), the place-matrix reconfiguring unit 23 deletes the layer setting 201 identified at Step S211411 from the place map information (Step S211416), and process proceeds to Step S2115 of FIG. 18.

Referring back to FIG. 18, the place-matrix reconfiguring unit 23 determines whether a place is moved at Step S19 (Step S2115). When the place-matrix reconfiguring unit 23 determines that operation other than move of the place is performed at Step S19 (No at Step S2115), process returns to Step S11 of FIG. 15.

On the other hand, at Step S2115, when determining that the place is moved at Step S19 (Yes at Step S2115), the place-matrix reconfiguring unit 23 performs an adjacency determination process based on place settings corresponding to the place before move and the place after move (Step S2116). The adjacency determination process at Step S2116 is described in detail below with reference to FIG. 21.

FIG. 21 is a flowchart illustrating a procedure of the adjacency determination process. The place-matrix reconfiguring unit 23 identifies the place setting 202 of a place before move, and the layer setting 201 containing that place setting 202, from the place map information (Step S211611).

Then, the place-matrix reconfiguring unit 23 detects at what position the place setting 202 identified at Step S211611 is contained in the layer setting 201 identified at Step S211611, that is, detects the place rank of that place setting 202 (Step S211612).

The place-matrix reconfiguring unit 23 checks the place rank detected at Step S211612, and determines whether the detected place rank is either at the second highest position or at the second lowest position (Step S211613). When the place-matrix reconfiguring unit 23 determines that the detected place rank is neither at the second highest position nor at the second lowest position (No at Step S211613), process returns to Step S11 of FIG. 15.

On the other hand, at Step S211613, when determining that the detected place rank is either at the second highest position or at the second lowest position (Yes at Step S211613), the place-matrix reconfiguring unit 23 detects at what position the layer setting 201 identified at Step S211611 is contained in the place map information, that is, detects the layer rank of that layer setting 201 (Step S211614).

Then, the place-matrix reconfiguring unit 23 checks the layer rank detected at Step S211614, and determines whether the detected layer rank is either at the second highest position or at the second lowest position (Step S211615). When the place-matrix reconfiguring unit 23 determines that the detected layer rank is neither at the second highest position nor at the second lowest position (No at Step S211615), process directly returns to Step S11 of FIG. 15.

On the other hand, at Step S211615, when determining that the detected layer rank is either at the second highest position or at the second lowest position (Yes at Step S211615), the place-matrix reconfiguring unit 23 performs the registration-status determination process on the place setting 202 corresponding to the place before move and the layer setting 201 containing that place setting 202, which are identified at Step S211611 (Step S211616). The registration-status determination process performed at Step S211611 is the same as that performed at Step S2114 of FIG. 20, and the same explanation is not repeated.

Then, the place-matrix reconfiguring unit 23 identifies the place setting 202 corresponding to a place after move, and the layer setting 201 containing that place setting 202, from place map information (Step S211617).

The place-matrix reconfiguring unit 23 then performs the edge determination process on the place setting 202 of the place after move and the layer setting 201 containing that place setting 202, which are identified at Step S211617 (Step S211618), and process proceeds to Step S11 of FIG. 15. The edge determination process performed at Step S211618 is the same as that performed at Step S2112 of FIG. 19, and the same explanation is not repeated.

The place map information whose setting content have been changed due to the place-matrix reconfiguration process at Step S21 is read in a process at Step S11. As a result, the updated place map information is displayed on the display unit 15.

In this manner, the place settings 202 contained in each of the layer settings 201 are displayed as places, each of which is used as unit for managing files, in the same hierarchy. When one place is selected from the displayed places, thumbnail images of files stored in association with the place setting 202 of the selected place are displayed on the display unit 15. Accordingly, a relationship between the places, each of which is a unit for managing files, can be intuitively recognized, and thereby, files can be effectively managed. Furthermore, because the places are displayed as a matrix, a relationship between the places can be orderly viewed in an array. As a result, the relationship between the places can be more effectively and intuitively recognized.

Next, operation performed by the searching unit 24 is described below with reference to FIGS. 22 to 24. FIG. 22 is a flowchart illustrating a procedure of a process for searching for a file from the place map screen (a map search process) performed by the searching unit 24.

The searching unit 24 waits for reception of character string (search key) to be a retrieval target from a user via the operating unit 14 (No at Step S31). When confirming that the search key is input (Yes at Step S31), the searching unit 24 refers to the layer attributes in the layer settings 201 contained in the place map information, and searches for the layer attribute corresponding to the search key (Step S32). The search can be performed by a full-text search or a truncated phrase search.

Through the search at Step S32, when the searching unit 24 determines that the layer attribute corresponding to the search key is not detected (No at Step S33), process directly proceeds to Step S35. On the other hand, through the search at Step S32, when determining that the layer attribute corresponding to the search key is detected (Yes at Step S33), the searching unit 24 extracts a place name registered in the place setting 202 from the layer setting 201 whose layer attribute corresponds to the search key (Step S34).

Then, the searching unit 24 refers to the place information stored in each of the “placeID” folders, and searches for the place attribute corresponding to the search key from the place attributes contained in the place information (Step S35).

Through the search at Step S35, when the searching unit 24 determines that the place attribute corresponding to the search key is not detected (No at Step S36), process directly proceeds to Step S38. On the other hand, through the search at Step S35, when determining that the place attribute corresponding to the search key is detected (Yes at Step S36), the searching unit 24 extracts a folder name of the “placeID” folder in which the place information containing the detected place attribute is stored, that is, extracts a place name (Step S37).

The searching unit 24 deletes redundant place names from place names extracted at Steps S34 and S37 (Step S38). Then, the searching unit 24 sequentially reads thumbnail images from each of the “placeID” folders corresponding to each of the place names obtained at Step S38 (Step S39). The searching unit 24 displays a list of the read thumbnail images on the display unit 15 (Step S40), and process ends. When no thumbnail images are read, that is, when a file corresponding to the search key is not detected, it is possible to display information indicating no files (e.g., not applicable) on the display unit 15.

In this manner, files can be retrieved from the place map screen based on attributes of the layers and the places. Therefore, files can be more effectively managed.

FIG. 23 is a flowchart illustrating a procedure of a search process (layer search process) performed when one or more layers are specified as refinement criteria from the place map screen. As a premise of the process, it is assumed that one or more layers are specified as the search area from the layers displayed on the place map screen by using the operating unit 14 (Step S51).

Under the condition of Step S51, the searching unit 24 waits for reception of a search key to be a retrieval target from a user via the operating unit 14 (No at Step S52). When receiving the search key (Yes at Step S52), the searching unit 24 refers to layer attributes contained in the layer settings 201 corresponding to the layer specified at Step S51 from among the layer settings 201 contained in the place map information, and searches for a layer attribute corresponding to the search key (Step S53).

Through the search at Step S53, when the searching unit 24 determines that the layer attribute corresponding to the search key is not detected (No at Step S54), process directly proceeds to Step S56. On the other hand, through the search at Step S53, when determining that the layer attribute corresponding to the search key is detected (Yes at Step S54), the searching unit 24 extracts the place name registered in the place setting 202 from the layer setting 201 whose layer attribute corresponds to the search key (Step S55).

The searching unit 24 then refers to the place information stored in the “placeID” folder corresponding to the place name of the place contained in the layer specified at Step S51, and searches for a place attribute corresponding to the search key from the place attributes contained in the place information (Step S56).

Through the search at Step S56, when the searching unit 24 determines that the place attribute corresponding to the search key is not detected (No at Step S57), process directly proceeds to Step S59. On the other hand, through the search at Step S56, when determining that the place attribute corresponding to the search key is detected (Yes at Step S57), the searching unit 24 extracts a folder name of the “placeID” folder in which the place information containing the detected place attribute is stored, that is, extracts a place name (Step S58).

The searching unit 24 then deletes redundant place names from place names extracted at Steps S55 and S58 (Step S59). Then, the searching unit 24 sequentially reads thumbnail images from each of the “contentsID” folders in the “placeID” folder corresponding to each of the place names obtained at Step S59 (Step S60). The searching unit 24 displays a list of the read thumbnail images on the display unit 15 (Step S61), and process ends.

In this manner, file search can be performed by refining the search area to a specified layer, i.e., file search can be performed for each of rows in the place matrix. Therefore, files can be more effectively managed.

FIG. 24 is a flowchart illustrating a procedure of a search process (place search process) performed when one or more places are specified as refinement criteria from the place map screen. As a premise of the process, it is assumed that one or more places are specified as the search area from the places displayed on the place map screen by using the operating unit 14 (Step S71).

Under the condition of Step S71, the searching unit 24 waits for reception of a search key to be a retrieval target from a user via the operating unit 14 (No at Step S72). When receiving the search key (Yes at Step S72), the searching unit 24 refers to the place information stored in the “placeID” folder corresponding to the place name of the place specified at Step S71, and searches for a place attribute corresponding to the search key from the place attributes contained in the place information (Step S73)

Through the search at Step S73, when the searching unit 24 determines that the place attribute corresponding to the search key is not detected (No at Step S74), process immediately ends. In this case, it is possible to display information indicating that no files are detected on the display unit 15.

On the other hand, through the search at Step S73, when determining that the place attribute corresponding to the search key is detected (Yes at Step S74), the searching unit 24 extracts a folder name of the “placeID” folder in which the place information containing the detected place attribute is stored, that is, extracts a place name (Step S75).

Then, the searching unit 24 sequentially reads thumbnail images from each of the “contentsID” folders in the “placeID” folder corresponding to the place name extracted at Step S75 (Step S76). The searching unit 24 then displays a list of the read thumbnail images on the display unit 15 (Step S77), and process ends.

In this manner, file search can be performed by refining the search area to a specified place. Therefore, files can be more effectively managed using place groups in a place matrix. It is also possible to perform file search by refining both layers and places. In this case, files can be retrieved with respect to refined rows and columns.

FIG. 25 is a perspective view illustrating an example of the file management apparatus 100, i.e., illustrating a configuration in which the display unit 15 that displays place map images, place view images, file view images, and the like is connected to the body of the file management apparatus. The display unit 15 is connected to the body of the file management apparatus 100 with a wire W such as a DVI cable, and data for displaying the place map images, the place view images, the file view images, and the like is input via the wire W.

Second Embodiment

A second embodiment of the present invention is described below. In the first embodiment, the file management apparatus 100 having a stand alone structure is explained on the premise that it is used by an individual user. In the second embodiment, a file management system having a server-client structure on the premise that it is used by a plurality of users will be explained. The same constituents as those of the first embodiment are denoted by the same reference numerals and symbols, and the same explanation is not repeated.

With reference to FIG. 26, a configuration of a file management system according to the second embodiment is explained. FIG. 26 is a block diagram illustrating the configuration of the file management system. As shown in the figure, the file management system includes a file management server 400 and a plurality of client terminals 500, which are communicably connected to one another via a network N.

The file management server 400 has the same file management function included in the file management apparatus 100 described above. The file management server 400 stores therein and manages files such as text, image, and video received (uploaded) from the client terminals 500.

FIG. 27 is a diagram illustrating a hardware configuration of the file management server 400. As shown in the figure, the file management server 400 includes a CPU 41, a ROM 42, a RAM 43, an operating unit 44 that includes an input device such as a mouse and a keyboard, a display unit 45 that includes a display device such as a liquid crystal display monitor, a storage unit 46 that includes a storage device such as an HDD, an I/F unit 47 that controls communication with external devices, and a bus 48 that connects the above units to one another. The exterior configuration of the file management server 400 is the same as that of the file management apparatus 100 shown in FIG. 25.

The ROM 42 and the storage unit 46 store therein various computer programs and various data. The CPU 41 loads the computer programs stored in the ROM 42 and the storage unit 46 onto the RAM 43, and executes the loaded computer programs to control the file management server 400 and realize various functional units to be described later.

The storage unit 46 manages files transmitted from a user (the client terminals 500), and stores/manages various types of setting information related to creation of a user interface for supporting the management of the files by using a predetermined folder structure. Details about the setting information stored and managed by the storage unit 46 will be described later.

Next, a functional configuration of the file management server 400 is described below. FIG. 28 is a block diagram illustrating the functional configuration of the file management server 400. As shown in the figure, the file management server 400 includes a login control unit 411, a file managing unit 412, a setting changing unit 413, a place-matrix reconfiguring unit 414, and a searching unit 415, as functional units realized by executing computer programs stored in the ROM 42 and the storage unit 46 by the CPU 41.

The login control unit 411 receives a login request (to be described later) from the client terminal 500 and performs authentication of a user by comparing a pair of a user ID and a password contained in the login request with a verification data that is stored in the storage unit 46 in advance. The verification data contains a pair of a user ID and a password of a user registered as a valid user. The user ID is identification information for identifying a user. For example, arbitrary character string indicating a nickname of a user or numbers indicating license numbers of a user, and the like can be used as the user ID.

The file managing unit 412 extracts the setting information associated with the user who has been authenticated as a valid user by the login control unit 411, and sends the setting information to the client terminal 500 from which the user attempts the login. A folder structure of the storage unit 46 for storing the setting information is described below with reference to FIG. 29.

FIG. 29 is a diagram illustrating a folder structure applied in the storage unit 46 for storing the setting information. As shown in the figure, the storage unit 46 contains a map managing section 210 corresponding to the map managing section 200, and a place managing section 310 corresponding to the place managing section 300.

The map managing section 210 is configured in units of user folders (user1, user2, etc.) created for each user (user ID) using the file management system. Each of the user folders contains place map information (placeMap.xml) for a user ID corresponding to a user folder name, an icon image (usericon.jpg) for the same user ID, and “userConfig.dat” for storing information about a user identified by the same user ID, such as a user name or a contact address (e.g., e-mail address).

The place managing section 310 contains “member.xml” for each “placeID” folder, in addition to the place information explained with reference to FIG. 3. The “member.xml” contains information about an owner of the “placeID” folder (namely, place) and user IDs of community members who share the “placeID” folder. Hereinafter, the “member.xml” is referred to as a member list. When a plurality of user IDs are registered in the member list, a corresponding place is shared by users identified by the user IDs registered on the member list. Hereinafter, a place shared by users is referred to as a shared place.

It is assumed that identification information for identifying an owner of a place is appended to a user ID of a user who has created the place corresponding to the “placeID” folder that contains the member list, among user IDs registered in the member list. Furthermore, access authority to be described later is granted to each of the user IDs of the community members of the place.

The file managing unit 412 reads the place map information associated with the user ID whose login has been permitted by the login control unit 411, and the “placeID” folder, from the storage unit 46. Then, the file managing unit 412 sends the place map information and the “placeID” folder to the client terminal 500.

Specifically, the file managing unit 412 identifies a user folder corresponding to the user ID whose login has been permitted, and reads the place map information from the map managing section 210 of the identified user folder. The file managing unit 412 also reads, from the place managing section 310, a “placeID” folder that is corresponding to the “placeID” contained in the place map information and that contains a member list in which the permitted user ID is registered.

When a user folder corresponding to the user ID whose login is permitted is not contained in the map managing section 210, that is, when the permitted user ID is a new user ID, the file managing unit 412 creates a new user folder whose folder name is identical to the new user ID in the map managing section 210. Then, the file managing unit 412 creates the map managing section 210 and the place managing section 310 under the created user folder. It is assumed that place map information contained in the created map managing section 210 is in state in which places are not set and a place matrix with three rows and three columns for example is set as an initial setting.

When the setting changing unit 413 and the place-matrix reconfiguring unit 414 update the setting information, the file managing unit 412 sends the updated setting information to the client terminal 500 thereby updating the setting information in the client terminal 500. The setting information to be sent can be differential data containing only updated pieces of data, or can be whole data containing all the setting information associated with the user ID being currently logged in.

When receiving a view request for instructing to view a specified file from the client terminal 500, the file managing unit 412 reads the specified file from the storage unit 46 and sends the read file to the client terminal 500 that has sent the view request.

When receiving a request for instructing to change settings of the place map screen or the place view screen, e.g., a request for instructing to register (upload) and delete files, change settings of layer names and place names, move and delete places, the setting changing unit 413 updates the setting information in the storage unit 46 based on the contents of the request.

The place-matrix reconfiguring unit 414 determines whether the place map information is updated due to update of the setting information by the setting changing unit 413. When determining that the place map information is updated, the place-matrix reconfiguring unit 414 performs the place-matrix reconfiguration process as described above, so that the place map information associated with the user ID that is contained in the request for changing the settings is updated.

When receiving a search request using a search key, such as attribute information (tag) appended to each of layers, places, and files, or character string (hereinafter, “keyword”), from the client terminal 500, the searching unit 415 searches through the storage unit 46 for a file corresponding to the search key.

When identifying a “contentsID” folder corresponding to the retrieved file from the place managing section 310, the searching unit 415 makes copies of data contained in the “contentsID” folder as well as a tree structure containing a “DD” folder and a “YYYYMM” folder to which the “contentsID” folder belongs, in the RAM 43 or a different storage location in the storage unit 46.

The searching unit 415 then merges the copy of the “contentsID” folder based on the date indicated by the “YYYYMM” folder and the “DD” folder, and creates a “placeID” folder containing files retrieved by the search (hereinafter, referred to as “a search result folder” as appropriate). It is assumed that the search result folder contains place information that contains correspondence between a folder name of each copy of “contentsID” folders and contents of place information stored in a “placeID” folder containing an original of each copy of the “contentsID” folders.

The searching unit 415 sends the created search result folder to the client terminal 500, as a search result of the search request.

Referring back to FIG. 32, the client terminal 500 is a terminal apparatus such as a PC and a mobile phone terminal to be operated by a user who uses the file management apparatus. In the embodiment, the client terminal 500 functions as a front end of the file management server 400. The client terminal 500 is configured such that a user can manage and view files uploaded to the file management server 400 by using a GUI, such as a place map screen, displayed on the client terminal 500. Assuming that the client terminal 500 is a PC, its external configuration is the same as that of the file management apparatus 100 shown in FIG. 25.

FIG. 30 is a diagram illustrating a hardware configuration of the client terminal 500. As shown in the figure, the client terminal 500 includes a CPU 51, a ROM 52, a RAM 53, an operating unit 54 that includes an input device such as a mouse and a keyboard, a display unit 55 that includes a display device such as a liquid crystal display monitor, a storage unit 56 that includes a storage device such as an HDD, an I/F unit 57 that controls communication with external devices, an adapter unit 58 to which a removable auxiliary storage device such as a memory card is attached, and a bus 59 that connects the above units to one another.

The ROM 52 and the storage unit 56 store therein various computer programs and various data. The CPU 51 loads the computer programs from the ROM 52 and the storage unit 56 onto the RAM 53, and executes the loaded computer programs to control the client terminal 500 and realize various functional units, which are described later

Next, a functional configuration of the client terminal 500 is described below. FIG. 31 is a block diagram illustrating the functional configuration of the client terminal 500. As shown in the figure, the client terminal 500 includes a login processing unit 511, a display control unit 512, a setting-change receiving unit 513, and a search-criteria receiving unit 514, as functional units realized by executing computer programs stored in the ROM 52 and the storage unit 56 by the CPU 51.

The login processing unit 511 displays a login screen for logging into the file management server 400 on the display unit 55. When receiving a user ID and a password from a user via the login screen, the login processing unit 511 sends a login request containing the user ID and the password to the file management server 400.

FIG. 32 is a diagram illustrating an example of the login screen displayed on the display unit 55 by the login processing unit 511. The login screen contains an area A31 in which a user ID (in this example, referred to as “quanp ID”) is entered and an area A32 in which a password is entered. When detecting that a button B31 for requesting login to the file management server 400 is pressed, the login processing unit 511 sends a login request containing at least a user ID entered in the area A31 and a password entered in the area A32 to the file management server 400.

Referring back to FIG. 31, the display control unit 512 displays a user interface, such as a place map screen as described above, on the display unit 55 based on data received from the file management server 400 via the I/F unit 57.

Specifically, when receiving the setting information sent from the file management server 400 when login is performed or when settings are changed, the display control unit 512 stores the received setting information in the RAM 53 or the storage unit 56 using the tree structure as shown in FIG. 3.

When receiving an operation for displaying a screen from a user via the operating unit 54, the display control unit 512 displays a place map screen, a place view screen, or a file view screen on the display unit 55 based on the setting information stored in the RAM 53 or the storage unit 56.

FIG. 33 is a diagram illustrating an example of the place map screen displayed on the display unit 55 by the display control unit 512. The figure illustrates a place map screen managed by a user whose user ID is “RICOH TARO” that is displayed in an area A41 by the display control unit 512. In the place map screen, three layer names “Family”, “Favorite”, “Work” are already set, and each layer contains places. For example, the layer named “Family” contains three places whose place names are “Party”, “Football”, and “Travel”. The layer named “Favorite” contains two places whose place names are “Home” and “Music”. The layer named “Work” contains one place whose place name is “Literature_Environmental Management”. The number displayed on the bottom portion of each place corresponds to the number of files stored (uploaded) in each place. The total number of files is derived from the total number of “contentsID” folders stored in each of “placeID” folders.

An area A42 is used for entering a search key to be used as a keyword for file search. A button B41 is used for starting search for a file corresponding to a search key entered in the area A42. That is, when the button B41 is pressed, the search key entered in the area A42 is sent to the search-criteria receiving unit 514. When a layer is selected from the place map screen, the selected layer is noticed as a search area with the search key to the search-criteria receiving unit 514.

Referring back to FIG. 31, the setting-change receiving unit 513 receives a request for changing setting of the place map screen and the place view screen, and sends a setting change request corresponding to the received request to the file management server 400, thereby requesting the file management server 400 to change the setting. Operation related to the change of the setting is, for example, registration, change, and deletion of layer names, layer attributes, and place name, as described above. When receiving such operation from a user via the operating unit 54, the setting-change receiving unit 513 sends to the client terminal 500 the operation content and information containing at least a user ID of a user who is logging in, as a setting change request.

The search-criteria receiving unit 514 receives input of a keyword as a search key and search criteria such as a search method described later, and sends a search request containing at least the search criteria and a user ID of a user who is logging in to the file management server 400, thereby requesting the file management server 400 to search for a file.

Operation for a file management process performed by the file management server 400 and the client terminal 500 is described below.

Display of a place map screen on the display unit 55 of the client terminal 500 is described below. FIG. 34 is a flowchart illustrating a flow of a process for displaying a place map screen by the file management server 400 and the client terminal 500. As a premise of the process, it is assumed that a user ID and a password of a user who operates the client terminal 500 are registered in advance in the file management server 400. It is also assumed that the user who uses the client terminal 500 is not invited to a shared place by other users.

The login processing unit 511 displays the login screen as shown in FIG. 38 before a user attempts to access the file management server 400 (Step S101). When determining that a login to the file management server 400 is requested us a result of detection that the button B31 is pressed, the login processing unit 511 sends a login request containing at least a user ID and a password entered in the login screen to the file management server 400 (Step S102).

In the file management server 400, when receiving the login request from the client terminal 500, the login control unit 411 performs authentication of the user by comparing a pair of the user ID and the password contained in the login request with verification data stored in the storage unit 46 (Step S111).

Through the authentication at Step S111, when determining that the pair of the user ID and the password contained in the login request do not match the verification data stored in the storage unit 46, that is, when determining that the user in not a valid user (No at Step S112), the login control unit 411 returns response information indicating that the login is denied to the client terminal 500 that has requested the login (Step S113), and process ends.

On the other hand, at Step S112, when determining that the pair of the user ID and the password contained in the login request match the verification data stored in the storage unit 46, that is, when determining that the user in a valid user (Yes at Step S112), the login control unit 411 returns response information indicating that the login is permitted to the client terminal 500 that has requested the login (Step S114), and process proceeds to Step S115.

In the client terminal 500, the login processing unit 511 receives the response information from the file management server 400 and determines whether the response information indicates that the login is permitted (Step S103). When the login processing unit 511 determines that the response information indicates that the login is denied (No at Step S103), process returns to Step S101 and the login screen is displayed again on the display unit 55. At this time, it is possible to display information indicating that the user ID and/or the password that have been entered are wrong on the display unit 55. When the response information indicates that the login is permitted (Yes at Step S103), process proceeds to Step S104.

In the file management server 400, when the login control unit 411 determines that the user is a valid user, the file managing unit 412 reads, from the storage unit 46, the setting information (place map information, etc.) associated with the user ID that is contained in the login request (Step S115), and sends the read setting information to the client terminal 500 that has requested the login (Step S116). When the user who is operating the client terminal 500 is invited to a shared place, a placeID name contained in the place map information (“Z” in <placeID=“Z”>) does not match a folder name of the “placeID” folder containing a member list in which the user ID of that user is registered, which will be explained later.

In the client terminal 500, when the display control unit 512 receives the setting information from the file management server 400, the display control unit 512 stores the received setting information in the RAM 53 or the storage unit 56 using the tree structure as shown in FIG. 3 (Step S104). Then, the display control unit 512 performs the place-map-screen display process based on the setting information stored at Step S104 to display the place map screen as shown in FIG. 38 on the display unit 55 (Step S105). The place-map-screen display process performed at Step S105 is the same as that performed at Step S11, and therefore, the same explanation is not repeated.

While the place map screen is being displayed, the setting-change receiving unit 513 keeps monitoring whether operation for changing setting content is input (No at Step S106). At Step S106, when determining that operation for changing setting content is input (Yes at Step S106), the setting-change receiving unit 513 sends a setting change request containing at least information indicating the operation content and the user ID of the user who is logging in, to the file management server 400 (Step S107).

In the file management server 400, when receiving the setting change request from the client terminal 500, the setting changing unit 413 identifies the setting information associated with the user ID contained in the setting change request from the storage unit 46 (Step S117). Then, the setting changing unit 413 updates the setting information identified at Step S117 based on the operation content contained in the setting change request (Step S118), and performs the place-matrix reconfiguration process on the place map information associated with the user ID (Step S119). The place-matrix reconfiguration process performed at Step S119 is the same as that performed at Step S21, and therefore, the same explanation is not repeated.

After Step S119, the file managing unit 412 reads the setting information updated at Step S118 from the storage unit 46, and sends the updated setting information to the client terminal 500 that has sent the setting change request (Step S120). Then, process ends.

For example, when receiving, at Step S106, operation for instructing to move a place named “Music” that is contained in the layer named “Favorite” to a place on the left side of the place named “Home” in the place map screen shown in FIG. 33, the setting-change receiving unit 513 sends a setting change request containing at least information for instructing the move of the place (e.g., information about the place before move and the place after move) and a user name “RICOH TARO” to the file management server 400.

In this case, the setting changing unit 413 exchanges a position of the place setting of the place before move and a position of the place setting of the place after move with each other from among the place settings associated with the user name “RICOH TARO”, so that the place is moved as requested by the user. In the place-matrix reconfiguration process at Step S119, the edge determination process that is the same as that performed at Step S2116 is performed; however, in this example, the place map is neither expanded nor reduced.

Furthermore, when subsequently receiving operation for instructing to register a new place with a place name “Movie” in a column on the right of the place named “Home”, the setting-change receiving unit 513 sends a setting change request containing at least information for instructing registration of the place with the place name “Movie” in the requested position and the user name “RICOH TARO” to the file management server 400. When a place name is registered, it is possible to display a support screen as shown in FIG. 35 by the setting-change receiving unit 513.

In FIG. 35, an area A51 is used for displaying the user ID of an owner of the place. Specifically, the user ID of a user who is logging in is displayed in the area A51 in a read-only mode. An area A52 is used for displaying a layer name of a layer in which the place is contained. Specifically, the layer name of a layer containing the place whose setting is to be changed is displayed in the area A52 in a read-only mode. An area A53 is used for entering a place name. An area A54 is used for entering a place attribute. When the place attribute is already set, the set place attribute is displayed in an area A55. An area A56 is used for entering arbitrary character string such as a comment to be associated with the place.

A button B51 is used for displaying a support screen for selecting an icon image to be displayed in the place. When the button B51 is pressed, the setting-change receiving unit 513 displays a support screen for selecting an icon image as shown in FIG. 36. FIG. 36 illustrates the screen for supporting selection of an icon image, and the screen is configured such that an arbitrary icon image can be selected from among image files stored in the storage unit 56 and icon images that are prepared in advance. When an icon image is selected and then a button B511 is pressed, contents entered and set in the support screen are sent to the setting-change receiving unit 513. In this case, the setting-change receiving unit 513 sends the setting change request to the file management server 400 by adding the selected icon image to the setting change request. When a button B512 is pressed, the setting-change receiving unit 513 closes the screen shown in FIG. 36.

Referring back to FIG. 35, when a user presses a button B52, contents entered and set in the screen is sent to the setting-change receiving unit 513. When a button B53 is pressed, the setting-change receiving unit 513 closes the screen. The support screens shown in FIGS. 35 and 36 are examples and the configuration of the support screens is not limited to these examples.

When receiving the setting change request containing at least information for instructing registration of the place with the place name “Movie” and the user name “RICOH TARO” from the client terminal 500, the setting changing unit 413 registers the place name “Movie” in the place setting of the requested place among place settings associated with the user name “RICOH TARO”, and registers the user ID “RICOH TARO” as an owner in the member list of the requested place. Therefore, the information entered and set in the screen shown in FIG. 35 is reflected in the setting information. When the icon image for the place is contained in the setting change request, the icon image is stored in a predetermined location (under the “placeID” folder).

FIG. 37 is a diagram illustrating an example of the place map screen displayed on the display unit 55 by the display control unit 512 after the operation described above has been performed. As shown in the figure, the place named “Music” is moved, and the place named “Movie” is newly registered in the requested place.

In this manner, the place information associated with each layer information is displayed as a place image, which is a unit for managing files, in the same hierarchy. Therefore, a relationship between the places can be intuitively recognized and files can be effectively managed. Furthermore, because the places are displayed as a matrix, a relationship between the places can be orderly viewed in an array. As a result, the relationship between the places can be more effectively and intuitively recognized.

Operation for changing setting of the member list is described below. FIG. 38 is a flowchart illustrating a flow of a process for changing setting of a shared place by the file management server 400 and the client terminal 500. As a premise of the process, it is assumed that the place map screen is being displayed on the display unit 55 of the client terminal 500.

The setting-change receiving unit 513 waits for reception of a request for changing setting of community members who share a specified place in the place map screen displayed on the display unit 55 (No at Step S131). The community members are users registered in the member list of each place.

When determining that change of setting of community members is instructed (Yes at Step S131), the setting-change receiving unit 513 displays a screen for supporting change of the setting of the community members on the display unit 55, based on the member list of the place whose setting of the community members is to be changed due to the request (Step S132).

FIG. 39 is a diagram illustrating an example of the screen for supporting setting of the community members, which is displayed at Step S132. In the figure, an area A61 is used for displaying a place name of a place whose setting of community members are to be changed. When a place name (placeID) is already registered in the place, the setting-change receiving unit 513 displays the place name in the area A61. When the place name is not registered in the place, as shown in FIG. 35, it is possible to display a notice (character string) for requesting a user to enter a place name such that the place name can be registered at the same time when the setting of the community members is completed.

An area A62 is used for displaying community members (user IDs) of the place whose setting of the community members is to be changed. The setting-change receiving unit 513 reads a member list of the place, for which the setting of the community members is instructed, and displays user IDs registered in the read member list in the area A62. A user of the client terminal 500 can select any user IDs displayed on the area A62. By selecting a user ID from the community members of the place and then pressing a button B61, it is possible to delete a specific user ID from the community members.

An area A63 is used for entering a user ID of a user to be registered in the member list of the place displayed in the area A61, that is, to be invited as a community member of the place (hereinafter, “invited user ID”). An area A631 is used for entering the invited user ID. An area A632 is used for entering an e-mail address of a user to be invited to the place. The user of the client terminal 500 can selectively use either an invited user ID or an e-mail address to invite a new user. When e-mail is selected, a message entered in an area A65, which will be described later, and information about invitation to be a community member of the place are sent to a user to be invited, via an e-mail system installed in the client terminal 500 or in the file management server 400.

Area A64 is used for setting access authority of a user to be invited to the place displayed in the area A61. The user of the client terminal 500 can set the access authority by selecting either one of radio buttons indicating “editor” and “reader” for the user to be invited via the area A63 (area A631). The “editor” represents authority for allowing a user to write (register and delete) and read files contained in the place. The “reader” represents authority for allowing a user only to read files contained in the place.

The area A65 is used for entering a message to the user to be invited to the place. That is, the user of the client terminal 500 can enter an arbitrary message in the area A65, and the entered message is sent to the user to be invited to the place. In the example shown in FIG. 39, it is assumed that a message must be within 500 words. However, the number of words is not limited to this example.

The button B61 is used for instructing deletion of a specified user ID from the community members. Specifically, when a user ID is selected from among user IDs displayed in the area A62, and then the button B61 is pressed, the setting-change receiving unit 513 sends a member deletion request containing a user ID of the user who is operating the client terminal 500, a place name of a place whose setting of the community members is to be changed, and a user ID to be deleted, to the file management server 400. When the selected user ID is the owner of the place, it is possible to inactivate the button B61 so that a user ID cannot be deleted.

A button B62 is used for registering a user invited in the area A63 to the community members of the place displayed in the area A61. Specifically, when information is entered and setting is completed in the areas A63 (A631) to A65 and then the button B62 is pressed, the setting-change receiving unit 513 sends a member registration request containing a user ID of the user who is operating the client terminal 500 (hereinafter, referred to as “operator user ID”), a place name of the place whose setting of the community members is to be changed, and contents entered and set from the areas A63 (A631) to A65, to the file management server 400.

When e-mail is selected in the area A63 as an invitation method, it is possible to send e-mail to the user to be invited from the client terminal 500. When the file management server 400 includes an e-mail system, it is possible to send e-mail to the user to be invited by using that e-mail system. In this case, the setting-change receiving unit 513 sends a member registration request containing the operator user ID, a place name of the place whose setting of the community members is to be changed, and contents entered and set from the areas A632 to A65, to the file management server 400.

A button B63 is used for terminating setting of the community members. When the button B63 is pressed, the setting-change receiving unit 513 closes the support screen shown in FIG. 39.

Referring back to FIG. 38, when receiving an instruction to delete or register a user ID with respect to a place whose setting of community members is to be changed, the setting-change receiving unit 513 sends a member setting request (the member deletion request or the member registration request) corresponding to the received request to the file management server 400 (Step S133).

In the file management server 400, when receiving the member setting request from the client terminal 500, the setting changing unit 413 identifies a member list corresponding to the operator user ID of the client terminal 500 and a place name of the place whose setting is to be changed, which are contained in the member setting request, from the storage unit 56 (Step S141).

The setting changing unit 413 determines whether the operator user ID contained in the member setting request is set as the owner in the member list identified at Step S141 (Step S142). When determining that the operator user ID is not set as the owner (No at Step S142), the setting changing unit 413 sends information indicating that operation is not permitted to the client terminal 500 that has sent the member setting request (Step S143), and process ends.

At Step S142, when determining that the operator user ID is set as the owner (Yes at Step S142), the setting changing unit 413 determines whether the member setting request is the member deletion request or the member registration request based on the contents of the member setting request (Step S144).

At Step S144, when determining that the member setting request is the member deletion request (No at Step S144), the setting changing unit 413 deletes the user ID specified by the member deletion request from the member list identified at Step S141 (Step S145), and process proceeds to Step S148.

At Step S144, when determining that the member setting request is the member registration request (Yes at Step S144), the setting changing unit 413 registers the invited user ID specified by the member registration request and appends access authority to the invited ID in the member list identified at Step S141, in an associated manner (Step S146). Then, the setting changing unit 413 registers a message contained in the member registration request for the invited user ID, in the “userconfig.dat” stored in the map managing section 210 associated with the invited user ID (Step S147), and process proceeds to Step S148.

At subsequent Step S148, the file management server 400 sends information indicating change of setting of the community members is completed and the member list updated at Step S145 or 5146 to the client terminal 500 that has sent the member setting request (Step S148), and process ends.

In the client terminal 500, the setting-change receiving unit 513 determines whether the information indicating change of setting of the community members is normally completed is received from the file management server 400 (Step S134). When determining that information indicating that operation is not permitted is received (No at Step S134), the setting-change receiving unit 513 displays information indicating that change of setting the community member is not permitted on the display unit 55 (Step S135), and process ends.

On the other hand, at Step S134, when receiving information indicating that change of setting of the community members is normally completed (Yes at Step S134), the setting changing unit 413 restores the updated member list received with the information in the RAM 53 or the storage unit 56, sc that the member list of the requested place is updated (Step S136).

In the above example, processes for inviting a user by sending an invited user ID as the user registration request are described. Alternatively, when an e-mail address of an invited user is to be used, the following process is applicable to register the invited user as a community member of the shared place. That is, when an e-mail address of each user is registered in each of “userconfig.dat” files, the file management server 400 searches for a “userconfig.dat” containing an e-mail address identical to the e-mail address of the invited user, and then registers a user ID associated with the retrieved “userconfig.dat” in the member list of the shared place.

When an e-mail address identical to the e-mail address of the invited user is not registered in any one of the “userconfig.dat” files, it is possible to store the e-mail address of the invited user in association with the shared place to which the user is invited. Then, when a new e-mail address of a new user is registered and the registered e-mail address corresponds to the stored e-mail address of the invited user, a user ID of the new user is registered in the member list of the invited place.

Operation performed by the client terminal 500 operated by a user who has invited to a shared place and the file management server 400 is descried below. FIG. 40 is a flowchart illustrating a flow of a process performed by the file management server 400 and the client terminal 500 when a user joins a shared place. As a premise of the process, it is assumed that a user ID of a user who is operating the client terminal 500 is registered in advance in the file management server 400. It is also assumed that the user who is operating the client terminal 500 is permitted to login to the file management server 400. The process shown in FIG. 40 is continued from Step S114 performed by the file management server 400 and Step S103 performed by the client terminal 500 in the process of FIG. 34.

In the file management server 400, when the login control unit 411 determines that the user is a valid user, the file managing unit 412 reads setting information associated with the user ID contained in the login request sent from the client terminal 500 (Step S161).

Then, the file managing unit 412 compares a place name registered in the place map information read at Step S161 with a folder name (place name) of each of “placeID” folders whose member list containing the user ID that is contained in the login request (Step S162). The file managing unit 412 then determines whether the place names are corresponding to each other (Step S163). At this time, a place name that is explicitly defined in the place map information is to be compared with the folder name at Step S162.

When determining that the place names are corresponding to each other (EQ at Step S163), the file managing unit 412 sends the setting information read at Step S161 to the client terminal 500 that has sent the login request (Step S164), and process ends. The processes performed at Steps S163 (EQ)→S164 are the same as those at Steps S115→S116.

When determining that more place names are registered in the place map information than those of existing “placeID” folders (DEL at Step S163), the file managing unit 412 determines that the user ID contained in the login request has been deleted from a member list of a shared place or the shared place itself has been deleted. Then, the file managing unit 412 causes the place-matrix reconfiguring unit 414 to perform the registration-status determination process on the place map information associated with the user ID contained in the login request (Step S165). The registration-status determination process performed at Step S165 is the same as that performed at Step S2114, and therefore, the same explanation is not repeated.

The file managing unit 412 sends additional information indicating that the shared place has been deleted and the setting information read at step S161 and containing the place map information processed at Step S165 to the client terminal 500 that has sent the login request (Step S166), and process ends. It is assumed that the additional information contains, as a place name of the shared place that has been deleted, a place name remained in the place map information after comparison at Step S163.

At Step S163, when determining that less place names are registered in the place map information than those of the existing “placeID” folders (ADD at Step S163), the file managing unit 412 determines that the user ID contained in the login request is invited to a shared place. The file managing unit 412 then sends additional information indicating invitation to the shared place and the setting information read at Step S161 to the client terminal 500 that has sent the login request (Step S167), and process proceeds to Step S168. It is assumed that the additional information contains a place name of a remaining “placeID” folder after comparison at Step S163.

In the client terminal 500, when receiving the setting information from the file management server 400, the display control unit 512 stores the setting information in the RAM 53 or the storage unit 56 (Step S151). Then, the display control unit 512 performs the place-map-screen display process based on the setting information stored at Step S151 to display the place map screen as shown in FIG. 33 on the display unit 55 (Step S152). The place-map-screen display process performed at Step S152 is the same as that performed at Step S11, and therefore, the same explanation is not repeated.

The display control unit 512 determines whether the additional information is received with the setting information (Step S153). When the display control unit 512 determines that the additional information is not received (No at Step S153), process ends.

At Step S153, when determining that the additional information is received (Yes at Step S153), the display control unit 512 determines whether the additional information indicates invitation to the shared place or deletion of the shared place (Step S154).

At Step S154, when determining that the additional information indicates deletion of the shared place (No at Step S154), the display control unit 512 displays a screen for notifying a place name of the shared place that has been deleted on the display unit 55 based on the additional information (Step S155), and process ends.

On the other hand, at Step S154, when determining that the additional information indicates invitation to the shared place (Yes at Step S154), the display control unit 512 displays a screen for confirming whether to join the shared place on the display unit 55 based on the additional information, the “userconfig.dat” that is the setting information stored in advance, and the member list of the shared place (Step S156).

FIG. 41 is a diagram illustrating an example of a screen displayed at Step S156 for confirming whether to join a shared place. In the figure, an area A71 is used for displaying information about the shared place to which a user who is operating the client terminal 500 is invited. The display control unit 512 displays the place name of the shared place, which is contained in the additional information, a user ID of the owner of the shared place (who opened the shared place), and an access authority of the invited user based on the member list of the shared place, in the area A71. An area A72 is used for displaying information about the shared place, other than information displayed in the area A71.

An area A73 is used for displaying a message to the user who is operating the client terminal 500 (the invited user ID). Specifically, information entered in the area A65 of FIG. 39, which is the message contained in the “userconfig.dat” by the owner of the shared place, is displayed in the area A73 by the display control unit 512.

The invited user can select whether to accept the invitation by pressing one of buttons B71 to B73 via the operating unit 54. The button B71 is used for accepting the invitation. When the button B71 is pressed, the user is continuously led to enter a position where the shared place is to be arranged in the place map screen. When receiving selection of the button B71, the setting-change receiving unit 513 sends response information containing information indicating acceptance of the invitation, the user ID of the user who is operating the client terminal 500, the place name of the shared place to which the user is invited, and information about a position where the shared place is to be arranged, to the file management server 400.

The button B72 is used for refusing invitation. When receiving selection of the button B72, the setting-change receiving unit 513 sends response information containing information indicating refusal of the invitation, the user ID of the user who is operating the client terminal 500, and the place name of the shared place to which the user is invited, to the file management server 400. The button B73 is used for holding an answer. When receiving selection of the button B73, the setting-change receiving unit 513 closes the screen shown in FIG. 41.

Referring back to FIG. 40, when determining that the user has held an answer about whether to accept the invitation via the support screen displayed at Step S156 (HOLD at Step S157), the setting-change receiving unit 513 closes the screen displayed at Step S156, and process ends.

At Step S157, when determining that the user has refused the invitation via the support screen displayed at Step S156 (REFUSAL at Step S157), the setting-change receiving unit 513 closes the support screen displayed at Step S156. Then, the setting-change receiving unit 513 sends the response information containing information indicating refusal of the invitation, the user ID who is operating the client terminal 500, and the place name of the shared place to which the user is invited, to the file management server 400 (Step S158). Then, process returns to Step S151 at which the display control unit 512 acquires the setting information from the file management server 400 in response to the response information.

At Step S157, when determining that the user has accepted the invitation via the support screen displayed at Step S156 (ACCEPTANCE at Step S157), the setting-change receiving unit 513 closes the support screen displayed at Step S156. Then, the setting-change receiving unit 513 sends the response information containing information indicating acceptance of the invitation, the user ID who is operating the client terminal 500, the place name of the shared place to which the user is invited, and a position where the shared place is to be arranged, to the file management server 400 (Step S159). Then, process returns to Step S151 at which the display control unit 512 acquires the setting information from the file management server 400 in response to the response information.

In the file management server 400, when receiving the response information from the client terminal 500, the setting changing unit 413 determines whether the response information indicates acceptance of the invitation based on the information contained in the response information (Step S168). When determining that the response information indicates refusal of the invitation (No at Step S168), the setting changing unit 413 deletes the user ID contained in the response information from the member list of the “placeID” folder corresponding to the place name contained in the response information (Step S169). Then, process proceeds to Step S172.

At Step S168, when determining that the response information indicates acceptance of the invitation (Yes at Step S168), the setting changing unit 413 identifies the place map information associated with the user ID contained in the response information from the map managing section 210, and sets the place name of the shared place to the place setting 202 at a position corresponding to the position of the shared place contained in the response information (Step S170).

Then, the setting changing unit 413 performs the edge determination process on the place map information whose setting is changed at Step S170 (Step S171), and process proceeds to Step S172. The edge determination process performed at Step S171 is the same as that performed at Step S2112, and therefore, the same explanation is not repeated.

At Step S172, the file managing unit 412 sends the setting information whose setting is changed, that is, the member list processed at Step S169 or the place map information processed at Steps s170 and S171 to the client terminal 500 that has sent the response information (Step S172). In the client terminal 500, when receiving the setting information sent at Step S172, the display control unit 512 stores the received setting information in the RAM 53 or the storage unit 56 at Step S151, thereby updating the setting information.

In this manner, place images can be provided for each user ID, so that the user can manage files by using own place images. Furthermore, a specific place image can be shared by a plurality of users, which is advantageous in that operation that requires a plurality of users to take part in, such as exchanging of files, can be performed easily. Moreover, a user who is invited to a shared place can select whether to accept the invitation to the shared place, so that usability of the user can be improved.

Next, operation for displaying the place view screen is described below. FIG. 42 is a flowchart illustrating a flow of a process for displaying the place view screen by the file management server 400 and the client terminal 500. As a premise of the process, it is assumed that the place map screen is being displayed on the display unit 55 of the client terminal 500.

The display control unit 512 waits for reception of an instruction to display a place view screen of a place specified from places displayed on the place map screen (No at Step S181). When determining that display of the place view screen is instructed (Yes at Step S181), the display control unit 512 refers to the “placeID” folder of the specified place from the place managing section 310 of the setting information stored in the RAM 53 or the storage unit 56, and performs the place-view-screen display process (Step S182). The place-view-screen display process performed at Step S182 is the same as that performed at Step S13, and therefore, the same explanation is not repeated.

At Step S182, the display control unit 512 displays the place view screen in a display mode corresponding to one of the place view screens G21 to G23 shown in FIG. 7. The display mode of the place-view screen is described in detail below.

FIG. 43 is a diagram illustrating an example of the place view screen in a display mode corresponding to the place view screen G21 shown in FIG. 7. In FIG. 43, files in a place named “Party” in the place map screen shown in FIG. 33 are displayed in the place view screen.

An area A81 is used for displaying thumbnail images of files registered in a place specified as a display target. In the display example shown in FIG. 43, the thumbnail images of files registered in the place specified as the display target are displayed three-dimensionally in the area A81 in the order of dates when the files are registered.

A cursor C1 is used for moving arrays of the thumbnail images to be displayed in the area A81. When the cursor C1 is moved upward or downward, the display control unit 512 moves arrays of the thumbnail images such that thumbnail images on farther lines or on nearer lines are scrolled in the area A81 of the place view screen. Consequently, temporally newer or older thumbnail images are displayed in the place view screen.

A cursor C2 is used for changing a display angle of the thumbnail images displayed in the area A81. When the cursor C2 is moved upward or downward, the display control unit 512 changes a view point (a depression angle) for displaying arrays of thumbnail images in a horizontal direction or a perpendicular direction in proportion to the amount of move of the cursor C2.

A cursor C3 is used for changing a place to be a display target of the place view screen. When the cursor C3 is moved to the left or to the right with respect to the place view screen, the display control unit 512 changes the display target to a place on the left side or on the right side of the place currently specified as the display target, based on positions of the places in the place map screen. Similarly, when the cursor C3 is moved upward or downward with respect to the place view screen, the display control unit 512 changes the display target to a place above or below the place currently specified as the display target, based on positions of the places in the place map screen. Then, the display control unit 512 performs the place-view-screen display process on the place specified as a new display target.

Operation for changing a display mode of the place view screen by moving the cursor C3 is described below with reference to FIGS. 44 to 47. FIG. 44 is a schematic diagram of the place map screen. In the figure, a unique symbol (A to E and a to d) is assigned to each row and each column, and each of places is uniquely identified by a combination symbol of corresponding row and column. For example, a place on the third column from the left (c) of the second layer (B) is identified by “Bc”. Similarly, a place on the second column from the left (b) of the third layer (C) is identified by “Cb”.

When a specific place (e.g., the place “Bc”) is specified from the place map screen shown in FIG. 44 by a user via the operating unit 54, the display control unit 512 displays a place view screen for the specified place.

FIG. 45 is a schematic diagram of a place view screen (the area A81) with respect to the place “Bc” shown in FIG. 44. In the figure, thumbnail images contained in “contentsID” folders stored in a “placeID” folder of the place “Bc” are displayed with symbols Bc1 to Bc12. The symbols Bc1 to Bc12 are associated with the symbol of the place “Bc”.

In the place view screen shown in FIG. 45, when the cursor C3 is moved to the left, the display control unit 512 changes a display target from the place “Bc” to a place “Bb” that is arranged on the left of the place “Bc” in the place map screen shown in FIG. 44. Then, the display control unit 512 displays a place view screen with respect to the place “Bb” as shown in FIG. 46. In the example shown in FIG. 46, eight thumbnail images registered in the place “Bb” are displayed with symbols Bb1 to Bb8 that are associated with the symbol of the place “Bb”.

When the cursor C3 is moved downward in the place view screen shown in FIG. 46, the display control unit 512 changes a display target from the place “Bb” to a place “Cb” that is arranged below the place “Bb” in the place map screen shown in FIG. 44. Then, the display control unit 512 displays a place view screen with respect to the place “Cb” as shown in FIG. 47. In FIG. 47, ten thumbnail images registered in the place “Cb” are displayed with symbols Cb1 to Cb10 that are associated with the symbol of the place “Cb”.

As described above, the cursor C3 is used for changing a place to be a display target of the place view screen, based on positions of places in the place map screen. When receiving a command indicating that the cursor C3 is moved either upward, downward, to the left, or to the right while the place view screen is displayed, the display control unit 512 changes a display target from a current place to a place on a corresponding side of the current place depending on a moving direction of the cursor C3. Thus, thumbnail images in the display target can be displayed by operation associated with positions of the places. As a result, a relationship between places, each of which is a unit for managing files, can be intuitively recognized, and thereby, files can be effectively managed. In the above example, it is assumed that the cursor C3 moves in four directions, that is, upward, downward, to the left, and to the right. However, there can be a configuration in which the cursor C3 moves in eight directions including four oblique directions as well as the above four directions.

Referring back to FIG. 43, a cursor C4 is used for changing display magnification of the place view screen displayed in the area A81. When the cursor C4 is moved to the left with respect to the place view screen (to the “−” side), the display control unit 512 reduces a display size of a group of thumbnail images displayed in the area A81 in proportion to the amount of move of the cursor C4. Similarly, when the cursor C4 is moved to the right with respect to the place view screen (to the “+” side), the display control unit 512 enlarges a display size of a group of thumbnail images displayed in the area A81 in proportion to the amount of move of the cursor C4.

An area A82 is used for displaying a layer name of a layer containing the place specified as the display target, a place name of the place, total size of files registered in the place, and the like. Such information is displayed by the display control unit 512 based on folder names of folders containing the thumbnail images displayed in the area A81, “content.xml” of each of the folders, the place map information, and the like.

Buttons B81 to B83 are used for changing a display mode of the place view screen. By selectively pressing one of the buttons B81 to B83, a user who is operating the client terminal 500 can change the display mode of the place view screen.

The button B81 is used for displaying a group of thumbnail images three-dimensionally as shown in FIG. 43. When receiving a command indicating that the button B81 is pressed, the display control unit 512 displays a group of thumbnail images three-dimensionally in the place view screen as shown in FIG. 43. In the example shown in FIG. 43, it is assumed that original files corresponding to the thumbnail images are image files. However, when original files are document files, such as text, contents of the document files are displayed in thumbnail images as shown in FIG. 48.

The button B82 is used for displaying thumbnail images two-dimensionally. When receiving a command indicating that the button B82 is pressed, the display control unit 512 two dimensionally displays thumbnail images of files registered in a place specified as a display target in the area A81 in the place view screen as shown in FIG. 49. The example shown in FIG. 49 corresponds to a display mode of the place view screen G22 shown in FIG. 7.

The button B83 is used for displaying a list of thumbnail images. When receiving a command indicating that the button B83 is pressed, the display control unit 512 displays a list of thumbnail images in the area A81 in the place view screen as shown in FIG. 50. The example shown in FIG. 50 corresponds to a display mode of the place view screen G23 shown in FIG. 7.

In FIG. 50, an area A83 is used for displaying information about files corresponding to thumbnail images. The display control unit 512 displays information such as a place name, a file name of a file, a file created date, a file updated date, a user name who has registered the file, and the like, based on the file information.

An area A84 is used for displaying contents or brief description of files corresponding to thumbnail images. In FIG. 50, it is assumed that original files corresponding to the thumbnail images are image files, so that no information is displayed in the area A84. Alternatively, in the example shown in FIG. 51, it is assumed that original files corresponding to thumbnail images are document files, so that parts of the contents of the document files are displayed as brief description in the area A84. It is assumed that the brief description is recorded in the file information of each of the files.

An area A85 shown in FIGS. 43 and 48 to 51 is used for entering a search key to be a keyword for file search. A button B84 is used for requesting search by the search key entered in the area A85. When the button B84 is pressed, the search key entered in the area A85 is sent to the search-criteria receiving unit 514.

Referring back to FIG. 42, the display control unit 512 determines whether change of the display mode is instructed by pressing one of the buttons B81 to B83 (Step S183). When the display control unit 512 determines that the change of the display mode is instructed (Yes at Step S183), process returns to Step S182 at which the display control unit 512 displays the place view screen in the requested display mode.

At Step S183, when the display control unit 512 determines that the change of the display mode is not instructed (No at Step S183), the setting-change receiving unit 513 determines whether registration of a file in the place that is a display target of the place view screen is instructed (Step S184). When the setting-change receiving unit 513 determines that the registration of a file is not instructed (No at Step S184), process proceeds to Step S188.

At Step S184, when determining that the registration of a file is requested (Yes at Step S184), the setting-change receiving unit 513 displays a support screen for registering a file on the display unit 55 and waits for reception of input from a user (Step S185).

FIG. 52 is a diagram illustrating an example of a screen for supporting registration of a file, which is displayed at Step S185. An area A91 is used for displaying a place name in which a file is to be registered. The setting-change receiving unit 513 displays a place name of a place in which a file is to be registered in the area A91. When registration of a file is requested from the place view screen, the file is to be registered in the place currently displayed in the place view screen. Therefore, the setting-change receiving unit 513 employs that place as a registration destination of the file.

An area A92 is used for displaying information about the file to be registered. The setting-change receiving unit 513 displays information such as a file name, a file type, and a file size of the file to be registered in the area A92.

An area A93 is used for entering an attribute to be appended to the file to be registered. A user can enter any arbitrary character string as an attribute of a file (hereinafter, referred to as “file attribute” as appropriate). An area A94 is used for entering a comment for the file to be registered. A user can enter any arbitrary character string as a comment.

A button B91 is used for requesting registration (upload) of a file. When receiving a command indicating that the button B91 is pressed, the setting-change receiving unit 513 sends a file registration request containing a file to be registered and a user ID of a user who is operating the client terminal 500 to the file management server 400 based on the information displayed and entered in the areas A91 to A94. A button B92 is used for canceling registration of a file. When receiving a command indicating that the button B92 is pressed, the setting-change receiving unit 513 closes the screen shown in FIG. 52.

It is not necessarily configured to specify and upload one file. For example, it is possible to specify and upload a plurality of files, or to specify a folder containing files to be uploaded. When the folder is specified, it is possible to also upload files stored in a sub folder which is nested in the specified folder (a folder inside the folder). In this case, it is possible to upload the files while maintaining information about a tree structure by adding tag information about in what sub folders the uploaded files are stored to the uploaded files.

The file upload process as described above is not necessarily performed upon reception of an instruction from a user, but it may also be performed as a background process in a period of time when a network is not busy. For example, it is possible to configure such that an upload instruction from a user is stored in an upload reservation list, that a monitoring tool for executing the background process is caused to refer to the upload reservation list at a timing such as a preset time, and that necessary upload processes are executed.

Referring back to FIG. 48, when receiving a request for registering a file from a user via the screen displayed at Step S185, the setting-change receiving unit 513 sends the above-mentioned file registration request to the file management server 400 (Step S186). When the file registration request is sent, it is possible to display a screen for notifying upload status of the file on the display unit 55 as shown in FIG. 53. A button B101 shown in FIG. 53 is used for cancelling sending of the file registration request. When the button B101 is pressed, the setting-change receiving unit 513 stops sending of the file registration request.

After Step S186, when receiving the setting information about the place in which the file has been registered from the file management server 400 as a response to the file registration request, the display control unit 512 updates the setting information stored in the RAM 53 or the storage unit 56 (Step S187). When information indicating that operation is not permitted, which will be described later, is received, this information is displayed on the display unit 55.

When determining that deletion of a file displayed on the place view screen (a thumbnail image) is instructed (No at Step S184→Yes at Step S188), the setting-change receiving unit 513 sends a file deletion request containing a folder name (contentsID) of a folder in which the thumbnail image to be deleted is stored, a place name of a place containing the folder, and a user ID of a user who is currently logging in, to the file management server 400 (Step S189).

After Step S189, when receiving from the file management server 400 the setting information about the place from which the file has been deleted as a response to the file deletion request, the display control unit 512 updates the setting information stored in the RAM 53 and the storage unit 56 (Step S190), and process returns to Step S182. When information indicating that operation is not permitted, which will be described later, is received, this information is displayed on the display unit 55.

At Step S188, when the setting-change receiving unit 513 determines that the deletion of a file is not instructed (No at Step S188), process returns to Step S182.

In the file management server 400, when receiving the file registration request or the file deletion request (Step S201), the setting changing unit 413 refers to a member list corresponding to the place to be processed due to the request, and determines whether the place is the shared place (Step S202). When the setting changing unit 413 determines that the place is not the shared place (No at Step S202), process proceeds to Step S205.

On the other hand, at Step S202, when determining that the place is the shared place (Yes at Step S202), the setting changing unit 413 determines whether an access authority of the user ID contained in the request received at Step S201 is a reader (only read is permitted) (Step S203). When determining that the access authority is the reader (Yes at Step S203), the setting changing unit 413 sends information indicating that operation on the file is not permitted to the client terminal 500 that has sent the file registration request or the file deletion request (Step S204), and process ends.

At Step S203, when determining that the access authority is an editor (read and write are permitted) (No at Step S203), the setting changing unit 413 identifies whether the request received at Step S201 is the file registration request or the file deletion request (Step S205). When identifying that the request is the file registration request (Yes at Step S205), the setting changing unit 413 performs a file registration process (Step S206). The file registration process performed at Step S206 is described in detail below with reference to FIG. 54.

FIG. 54 is a flowchart illustrating a procedure of the file registration process. The setting changing unit 413 stores a file that is contained in the file registration request as a file to be registered, in a predetermine location of the storage unit 46 (Step S20601). At this time, the file can be stored in arbitrary storage location. For example, the file can be stored and managed in database, or in an external storage device other than the storage unit 46.

The setting changing unit 413 acquires current date from the timing unit (not shown) that counts date and time (Step S20602), and creates a “YYYYMM” folder and a “DD” folder corresponding to the current date, in a predetermined structure under a place to be processed (Step S20603). When the “YYYYMM” folder and the “DD” folder corresponding to the current date are already created, this process is omitted.

Then, the setting changing unit 413 creates a “contentsID” folder corresponding to a file name of the file to be registered, under the “DD” folder created at Step S20603 (Step S20604). The setting changing unit 413 creates a thumbnail image from the file created at Step S20601 (Step S20605), and stores the created thumbnail image in the “contentsID” folder created at Step S20604 (Step S20606).

The setting changing unit 413 creates file information (content.xml) (Step S20607). The file information contains information contained in the file registration information (e.g., user ID, information about the file), and the storage location of the file stored at Step S20601. When the file stored at Step S20601 is a document file, the setting changing unit 413 analyzes contexts or phrases in the file, creates a summary as a brief description of the document file, and stores the summary in the file information. The analysis of the contexts or phrases can be performed by using known technique.

The setting changing unit 413 then stores the file information created at Step S20607 in the “contentsID” folder created at Step S20604 (Step S20608), and process control proceeds to Step S208 of FIG. 42.

Referring back to FIG. 42, when determining that the request is the file deletion request (No at Step S205), the setting changing unit 413 performs a file deletion process based on the file deletion request (Step S207). The file deletion process is described in detail below with reference to FIG. 55.

FIG. 55 is a flowchart of a procedure of the file deletion process performed at Step S207. The setting changing unit 413 identifies a “contentsID” folder corresponding to a file name of a file to be deleted from the “placeID” folder corresponding to the place name contained in the file deletion request (Step S20701).

The setting changing unit 413 refers to the file information stored in the “contentsID” folder identified at Step S20701, and deletes a file to be deleted from the storage location contained in the file information (Step S20702).

Then, the setting changing unit 413 determines whether other “contentsID” folders are contained in the “DD” folder that contains the “contentsID” folder identified at Step S20701 (Step S20703). When determining that other “contentsID” folders are not contained (No at Step S20703), the setting changing unit 413 deletes the “DD” folder (Step S20704), and process proceeds to Step S208 of FIG. 42.

On the other hand, at Step S20703, when determining that other “contentsID” folders are contained (Yes at Step S20703), the setting changing unit 413 deletes only the “contentsID” folder identified at Step S20701 (Step S20705), and process proceeds to Step S208 of FIG. 42.

Referring back to FIG. 42, the setting changing unit 413 sends the setting information updated at Step S206 or S207 to the client terminal 500 that has sent the file registration request or the file deletion request (Step S208), and process ends. In the client terminal 500, the setting information is updated at Step S190, so that the updated place view screen is displayed on the display unit 55.

Operation for viewing a file specified from files (a group of thumbnail images) displayed on the place view screen is described below. FIG. 56 is a flowchart illustrating a flow of a process for viewing a file, performed by the file management server 400 and the client terminal 500. As a premise of the process, it is assumed that the place view screen is being displayed on the display unit 55 of the client terminal 500.

The setting-change receiving unit 513 waits for reception of an instruction to display a file whose thumbnail image is specified from thumbnail images displayed on the place view screen (No at Step S211). When determining that the display of the file is instructed (Yes at Step S211), the setting-change receiving unit 513 reads the storage location of a file corresponding to the specified thumbnail image, from the file information in a folder (“contentsID” folder) containing the specified thumbnail image (Step S212). Then, the setting-change receiving unit 513 sends a file view request containing information about the storage location read at Step S212 to the file management server 400 (Step S213).

In the file management server 400, when receiving the file view request, the file managing unit 412 reads the file from the storage location contained in the file view request (Step S221). Then, the file managing unit 412 sends the file read at Step S221 to the client terminal 500 that has sent the file view request (Step S222), and process ends.

In the client terminal 500, when receiving the file from the file management server 400 as a response to the file view request, the display control unit 512 displays a file view screen in a display mode of one of the file view screen G31 to G33 shown in FIG. 7 (Step S214). The display mode of the file view screen is described below.

FIG. 57 is a diagram illustrating an example of a file view screen in a display mode corresponding to the file view screen G31 of FIG. 7. In the figure, an area A111 is used for displaying a file that is a display target, that is, for displaying a file sent from the file management server 400 with respect to each page. An area A112 is used for displaying a thumbnail image of each page contained in the file. In FIG. 57, only one thumbnail image is displayed in the area A112 because the file contains only one image file. However, when a file contains a plurality of pages, a plurality of thumbnail images of the pages are displayed in the area A112 as shown in FIG. 58.

When receiving a command indicating that one thumbnail image is selected from thumbnail images of corresponding pages displayed in the area A112, or that a page is specified by using a cursor C111, the display control unit 512 displays the specified page in the area A111. It is assumed that, the first page of the specified file is displayed in the area A111 in the default state.

An area A113 is used for displaying all thumbnail images of all files registered in a place that contains a file specified as a display target. The display control unit 512 identifies a “placeID” folder containing a thumbnail image of the file specified as the display target by the user, reads thumbnail images from all the “contents ID” folders contained in the identified “placeID” folder, and displays the read thumbnail images in the area A113. When a thumbnail image of another file is specified from the area A113, processes from Step S212 to Step S214 are performed on the specified thumbnail image to display the file view screen with respect to a file corresponding to the specified thumbnail image.

An area A114 is used for displaying various information about a file specified as a display target. Specifically, the display control unit 512 displays a place name or a layer name of a place or a layer containing a “contentsID” folder corresponding to the file specified as the display target, and information about the file, such as a file name, a file created date, a file updated date, a file type, a file size, and an owner (creator) of the file, in the area A114 based on the file information or the information appended to the file.

An area A115 is used for displaying a comment for the file that is entered when the file is registered, or a file attribute (tag). Specifically, the display control unit 512 reads a comment entered for the file or a file attribute from the file information corresponding to the file specified as the display target, and displays the read information in the area A115. In FIG. 57, it is assumed that the comment and the file attribute are displayed using tabs. However, the information can be displayed in other ways.

A cursor C111 is used for specifying a page number of a page to be displayed in the area A111. When one of cursor buttons arranged in the middle of the cursor C111 indicating a right direction and a left direction with respect to the screen is pressed, the display control unit 512 retrieves a page corresponding to a forwarded page number or a reversed page number from the file specified as the display target, and then displays the read page in the area A111. Cursor buttons at edges of the cursor C111 are used for displaying the first page and the last page from the file.

A cursor C112 is used for changing display magnification of a file screen displayed in the area A111. When the cursor C112 is moved to the left with respect to the file view screen (“−” side), the display control unit 512 reduces the display size of the file screen displayed in the area A111 in proportion to the amount of move of the cursor C112. Similarly, when the cursor C112 is moved to the right with respect to the file view screen (“+” side), the display control unit 512 enlarges the display size of the file screen displayed in the area A111 in proportion to the amount of move of the cursor C112.

Buttons B111 to B113 are used for changing a display mode of the file view screen. The button B111 is used for requesting a display mode in which a file specified as a display target and thumbnail images of other files registered in the same place are displayed. When receiving a command indicating that the button B111 is pressed, the display control unit 512 displays the file view screen in the display mode as shown in FIGS. 57 and 58.

A button B112 is used for requesting a display mode in which only a file specified as a display target is displayed as shown in FIG. 59. When receiving a command indicating that the button B112 is pressed, the display control unit 512 displays the file specified as the display target in the area A111. Thus, the file view screen in the display mode as shown in FIG. 65 is displayed. The example shown in FIG. 59 corresponds to the display mode of the file view screen G32 shown in FIG. 7.

A button B113 is used for requesting a display mode in which a list of thumbnail images of pages contained in a file specified as a display target is displayed as shown in FIG. 60. When receiving a command indicating that the button B113 is pressed, the display control unit 512 displays thumbnail images created from pages contained in the file specified as the display target in the area A112, so that the file view screen in the display mode as shown in FIG. 60 is displayed. The example shown in FIG. 60 corresponds to the display mode of the file view screen G33 shown in FIG. 7. In this display mode, upon receiving a selection of a thumbnail image from among the thumbnail images displayed in the area A112 from a user, the display control unit 512 displays the page corresponding to the selected thumbnail image in the display mode shown in FIG. 57 or FIG. 59.

A button B114 is used for closing the file view screen. When receiving a command indicating that the button B114 is pressed, the display control unit 512 closes the file view screen and subsequently displays a place view screen.

Operation for changing the display mode among the above-described file view screens is described below with reference to FIGS. 61 to 63. Similarly to the examples shown in FIGS. 44 to 47, in FIGS. 61 to 63, it is assumed that each of places is uniquely identified by a combination symbol of corresponding row and column (A to F and a to d) based on positions in the place matrix. Furthermore, each of thumbnail images (files) stored in each of the places is uniquely identified by a sequence number appended to the symbol of the place.

FIG. 61 is a schematic diagram of a file view screen in a display mode shown in FIGS. 57 and 58. FIG. 61 illustrates a file view screen in which a file “Bc1” is displayed from among thumbnail images stored in a “placeID” folder corresponding to a place “Bc”. In the area A111, the second page of the file “Bc1” is displayed, in which the page is identified by “Bc1-2”. In this case, thumbnail images of other pages (“Bc1-1” to “Bc1-4”) contained in the file “Bc” are displayed in the area A112. In the area A113, thumbnail images of other files (“Bc1” to “Bc7”) stored in the “placeID” folder of the place “Bc” are displayed.

FIG. 62 is a schematic diagram of a file view screen in a display mode shown in FIG. 59. When the second page of the file “Bc1” is displayed similar to the example shown in FIG. 61, only a page image “Bc1-2” is displayed in the area A111 as shown in FIG. 62. FIG. 63 is a schematic diagram of a file view screen in a display mode shown in FIG. 60. When the file “Bc1” is displayed, as shown in FIG. 63, thumbnail images of four pages (“Bc1-1” to “Bc1-4”) contained in the file “Bc1” are displayed in the area A112.

Referring back to FIG. 56, the display control unit 512 determines whether change of the display mode is requested (Step S215). When the display control unit 512 determines that the change of the display mode is requested (Yes at Step S215), process returns to Step S214 at which the display control unit 512 displays a file view screen in the requested display mode.

On the other hand, at Step S215, when determining that the change of the display mode is not requested (No at Step S215), the display control unit 512 determines whether other file is selected as a display target (Step S216). When the display control unit 512 determines that no files are selected as a display target (No Step S216), process ends. On the other hand, when determining that other file is selected as a display target (Yes Step S216), process proceeds to Step S212 at which a file view request for the selected file is sent to the file management server 400.

Third Embodiment

A system according to a third embodiment of the present invention is illustrated in FIG. 64. The embodiment employs a server-client structure similar to the second embodiment, where a client terminal and a server block 600 are communicably connected to each other via a network N. Here, Web browser 501 a, dedicated client software 501 b, and registered mail software 501 c are applicable as the client terminals composed of PC and the like. Further, mobile phone 5001 is also applicable as the client terminal.

The server block 600 includes a firewall 6001, a communication control unit 6002, a main control unit 6003, an image processing unit 6004, and a data accumulating unit 6005.

The communication control unit 6002 includes an Web server 60021 and a mail server 60022. The main control unit 6003 includes an authentication control unit 60031, a place control unit 60032, a contents control unit 60033, a search sorting unit 60034, a mail control unit 60035, and a platform (framework) RoR 60036. The image processing unit 6004 includes an image processing server 60041. The data accumulating unit 6005 includes a metadata accumulating unit 60051, an index accumulating unit 60052, and a binary-data accumulating unit 60053.

The authentication control unit 60031, the place control unit 60032, the contents control unit 60033, and the search sorting unit 60034, included in the main control unit 6003, have the structures similar to those of the login control unit 411, the file managing unit 412, and the searching unit 415 of the file management server 400 shown in FIG. 28 (the second embodiment). The mail control unit 60035 performs control so that the contents and attached files of mails from the client terminals such as PCs and mobile phone terminals can be registered as contents data.

In the metadata accumulating unit 60051 and the binary-data accumulating unit 60053 in the data accumulating unit 6005, meta data and binary data are accumulated using hierarchical structures, respectively. The hierarchical structure of the contents data is illustrated in FIG. 65. As shown in the figure, a four-level hierarchical structure is employed, and the second level in the hierarchy is divided into two areas for binary data related to images and metadata being management data. The metadata is further divided into two pieces of information, i.e., bibliographic information related to files and owner information related to owners, in the third level in the hierarchy. Although it is not illustrated, in the case of the place data, only metadata is provided in the second level in the hierarchy, and the meta data is divided into place information and place owner information in the third level in the hierarchy.

With this hierarchical structure, it is possible to effectively accumulate and manage information. Furthermore, even when the contents and places are changed at the client side, it is possible to accumulate and manage latest updated information in the server side at any time. With this function, the latest contents information and the latest place information can be shared in the operation and browsing without causing confusion in sharing operations and reference.

Next, details of the image processing server 60041 is described below. FIG. 66 illustrates a relation of connection from the client terminal 500 to the image processing server 60041 in the server block 600. FIG. 67 illustrates an internal block of the image processing server 60041 and its input/output data.

The image processing server 60041 generates thumbnails and bitmap images so that contents of files can be viewed by a display unit of the client terminal 500 without using application. As a means for creating these images, the image processing server 60041 includes an image converting unit 600411 and an image magnification changing unit 600412.

The image converting unit 600411 eventually converts files into bitmaps when a type of an input file (extension) is “.doc”, “.xls”, “.ppt”, and the like. In this case, it is possible to convert the file into a PDF file (with extension of “.pdf”) as an intermediate process, and then possible to convert the PDF file into a bitmap. In FIG. 67, a pdf converting unit 6004111 and a jpeg converting unit 6004112 perform this process. The image magnification changing unit 600412 generates bitmap images and thumbnail images of a size corresponding to a display size of the display means of the client terminal 500 based on the bitmap data output from the image converting unit 600411. The created image data is to be accumulated in the binary-data accumulating unit 60053.

In FIG. 66, a file retrieval instruction transmitted from the client terminal is input into the server block 600 via the network N, and then is input into the image processing server 60041, through the Web server 60021, the RoR 60036, and then a file server 6006.

The image processing server 60041 operates as follows according to the input file retrieval instruction. That is, the image processing server 60041 outputs thumbnail data when application that runs on the client terminal 500 is determined to be a slide-show tool, outputs HTML data when the application that runs on the client terminal 500 is determined to be an Web browser, and outputs Flash data when the client terminal 500 is determined to be a mobile phone terminal. These image data are transmitted to the client terminal 500 via the network N through the file server 6006, the RoR 60036, and the Web server 60021, and are displayed on the display unit of the client terminal 500.

The present invention is not limited to the specific details described in the above embodiments. Accordingly, various modifications can be made without departing from the scope of the present invention. Furthermore, various inventions can be made by combining the constituent elements described in the above embodiments. Furthermore, part of the constituent elements can be removed from whole of the constituent elements or the constituent elements described in different embodiments can be integrated as appropriate.

For example, the computer programs executed in various processes performed by the above-described apparatuses can be stored in computers connected to a network such as the Internet so that the computer programs can be downloaded via the network as appropriate.

The computer programs executed by the above-described apparatuses can be stored in a storage medium such as a ROM for distributing the computer programs.

It is assumed that the setting information for displaying a user interface is stored by using the structure shown in FIGS. 3 and 29. However, the setting information can be stored by using other structures. Furthermore, it is assumed that the setting information is stored in xml format in the above embodiments. However, the setting information can be stored in other formats.

Moreover, the management method implemented with respect to each user in the second embodiment can be applied to a stand-alone type apparatus as described in the first embodiment. In this case, the setting information stored in the storage unit 16 of the file management apparatus 100 can stored not only by using the folder structure shown in FIG. 29 but also by using other structures.

According to one aspect of the present invention, contents of files can be viewed by a display unit of a client terminal without using application.

Although the invention has been described with respect to specific embodiments for a complete and clear disclosure, the appended claims are not to be thus limited but are to be construed as embodying all modifications and alternative constructions that may occur to one skilled in the art that fairly fall within the basic teaching herein set forth. 

1. A file management apparatus connected to a client terminal via a network, the file management apparatus comprising: a file receiving unit that receives a file transmitted from the client terminal; an image processing unit that generates bitmap data and thumbnail data according to the file received by the file receiving unit; a file storage unit that stores therein each of the bitmap data and the thumbnail data generated by the image processing unit, in association with the file; a receiving unit that receives a file retrieval instruction transmitted from the client terminal; a determining unit that determines a type of the client terminal or a type of application that runs on the client terminal, based on the file retrieval instruction received by the receiving unit; and an output unit that outputs one of the file, the bitmap data, and the thumbnail data stored in the file storage unit according to a result of determination performed by the determining unit.
 2. The file management apparatus according to claim 1, wherein when the determining unit determines that the application that runs on the client terminal is a slide-show tool, the output unit outputs the thumbnail data to the client terminal.
 3. The file management apparatus according to claim 1, wherein when the determining unit determines that the client terminal is a mobile phone terminal, the output unit outputs Flash data to the client terminal.
 4. The file management apparatus according to claim 1, wherein when the determining unit determines that the application that runs on the client terminal is an Web browser, the output unit outputs HTML data to the client terminal. 